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

@vulcantech/banners

v0.1.1

Published

CMS-driven announcement banners for consumer sites — top/bottom positions, page targeting, priority ordering, and dismissible bars backed by localStorage

Readme

@vulcantech/banners

CMS-driven announcement banners for VulcanTech consumer sites. Renders top/bottom bars fetched from the CMS, with page targeting, priority ordering, and per-user dismissal (localStorage).

Exports: CMSBanners (drop-in layout component), BannerBar (single bar), and the BannerData type.

Integration

Wire banners into a consumer site (Next.js App Router):

1. Add the dependency:

npm install @vulcantech/banners

(Inside the VulcanTech monorepo, use the workspace wiring in MONOREPO.md instead.)

2. Set the env — see Required env below.

3. Create the server fetcher src/lib/cms/banners.ts (ISR-cached, fails open):

import type { BannerData } from "@vulcantech/banners";

const CMS_URL = process.env.VULCANTECH_CMS_URL || "https://cms.vulcantech.io";
const PROJECT_ID = process.env.VULCANTECH_PROJECT_ID;
const API_KEY = process.env.VULCANTECH_API_KEY;

export async function fetchBanners(): Promise<BannerData[]> {
  if (!PROJECT_ID || !API_KEY) return [];
  const params = new URLSearchParams({ projectId: PROJECT_ID, apiKey: API_KEY });
  try {
    const res = await fetch(`${CMS_URL}/api/banners?${params}`, {
      next: { revalidate: 60, tags: [`banners:${PROJECT_ID}`] },
    });
    if (!res.ok) return [];
    const json = (await res.json()) as { banners: BannerData[] };
    return json.banners ?? [];
  } catch {
    return [];
  }
}

4. Render in the root layout (src/app/layout.tsx):

import { CMSBanners } from "@vulcantech/banners";

const banners = await fetchBanners();
// <body>
//   <CMSBanners banners={banners} position="top" />
//   {children}
//   <CMSBanners banners={banners} position="bottom" />
// </body>

5. ISR invalidation — ensure src/app/api/revalidate/route.ts exists; the CMS purges the banners:{projectId} tag when a banner is edited.

Required env

VULCANTECH_PROJECT_ID, VULCANTECH_API_KEY (required) · VULCANTECH_CMS_URL (optional, defaults to https://cms.vulcantech.io).

Per-app values

None beyond env — banners is fully config-driven from the CMS.

Notes

  • Components are "use client"; dismissal persists to localStorage (vulcantech_dismissed_banners).