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

@signap/signals-nextjs

v2.1.0

Published

SSR-safe Next.js wrapper for @signap/signals-web

Readme

@signap/signals-nextjs

SSR-safe wrapper for @signap/signals-web targeting Next.js 14/15 (App Router).

Install

pnpm add @signap/signals-nextjs
# next/react are peerDependencies

Usage (App Router)

// app/layout.tsx — Server Component
import { SignalsScript } from "@signap/signals-nextjs";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        <SignalsScript
          apiKey={process.env.NEXT_PUBLIC_SIGNALS_API_KEY!}
          endpoint={process.env.NEXT_PUBLIC_SIGNALS_ENDPOINT!}
        >
          {children}
        </SignalsScript>
      </body>
    </html>
  );
}
// app/page.tsx — Server Component that contains a Client Component
import { VisitorBadge } from "./visitor-badge";
export default function Page() { return <VisitorBadge />; }
// app/visitor-badge.tsx
"use client";
import { useVisitorData } from "@signap/signals-nextjs";

export function VisitorBadge() {
  const { data, isLoading } = useVisitorData({ tag: "homepage" });
  if (isLoading) return null;
  return <span>visitor: {data?.visitorId}</span>;
}

v2 (ADR §A2) returns the resolved visitor in a single round-trip — no separate ack/lookup transition. See the @signap/signals-react README for the full shape.

Endpoint discovery

SignalsScript spreads AgentLoadOptions, so pass an endpoint callback to resolve the endpoint at runtime — e.g. for region routing. See the @signap/signals-web README (Endpoint section).

<SignalsScript apiKey={process.env.NEXT_PUBLIC_SIGNALS_API_KEY!} endpoint={async () => (await myConfig()).ingestEndpoint} />

SSR-safe contract

  • @signap/signals-nextjs and @signap/signals-react import cleanly into Server Components — module evaluation touches no browser APIs.
  • SignalsScript carries the "use client" directive itself; everything reachable from it runs on the client only.
  • The agent loads inside useEffect, never during render or hydration.
  • Public env vars: NEXT_PUBLIC_* only carry the public apiKey (pk_live_*). Server-only secrets must never appear under NEXT_PUBLIC_.