npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pixelstackai/nuxt

v0.1.0

Published

Nuxt module for Pixelstack

Readme

@pixelstackai/nuxt

The Nuxt module for Pixelstack: render your designs with a <PixelstackImage> component, with signed URLs built on the server.

Install

npm install @pixelstackai/nuxt
export default defineNuxtConfig({
  modules: ['@pixelstackai/nuxt'],
  pixelstack: {
    teamId: 'your-team-id',
    signingSecret: process.env.PIXELSTACK_SIGNING_SECRET,
  },
});

Find your team ID and signing secret in Team settings in the Pixelstack app. You only need the signing secret if your designs require signed URLs. It's kept in the server's runtime config, so it never reaches the browser.

Usage

<template>
  <PixelstackImage
    src="my-design"
    alt="Welcome banner"
    :data="{ title: { text: 'Hello World' } }"
    :variables="{ 'profile-url': 'https://example.com/ada' }"
  />
</template>

src is the design's ID, data sets values on its objects, by object ID and property, and variables sets the variables of its workflow, by variable ID. Other attributes are passed to the <img>.

usePixelstackImage and getPixelstackImageUrl take data and variables too.

For the URL alone, use the usePixelstackImage composable, for example for an Open Graph image:

const { data: image } = usePixelstackImage({
  designId: 'my-design',
  data: { title: { text: 'Hello World' } },
});

useSeoMeta({ ogImage: () => image.value?.url });

Signed URLs

Your signing secret only exists on the server, so URLs are only signed when they're built there.

<PixelstackImage> and usePixelstackImage build the URL on the server when the page is server-rendered or prerendered, so it's signed. When a visitor navigates to the page from another page of your app, the URL is built in the browser, so it isn't signed. That's fine for Open Graph images, which crawlers read from the server-rendered page, and for designs that don't require signed URLs.

For signed URLs on every navigation, build them in your server routes with getPixelstackImageUrl. It's auto-imported in your server/ directory:

// server/api/posts/[id].get.ts
export default defineEventHandler(async (event) => {
  const post = await getPost(getRouterParam(event, 'id'));

  return {
    ...post,
    bannerUrl: getPixelstackImageUrl('my-design', { data: { title: { text: post.title } } }),
  };
});
<script setup lang="ts">
const route = useRoute();
const { data: post } = await useFetch(`/api/posts/${route.params.id}`);
</script>

<template>
  <img :src="post?.bannerUrl" alt="Banner" />
</template>

Keep getPixelstackImageUrl behind routes that decide the data themselves. A route that signs whatever the browser sends would let anyone sign any image.

Documentation

See docs.pixelstack.io.

License

MIT