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

@jlaviole90/tracker-next

v0.1.6

Published

Next.js bindings for @jlaviole90/tracker. Supports App Router and Pages Router.

Readme

@jlaviole90/tracker-next

Next.js adapter for @jlaviole90/tracker.

  • App Router — drop <Webalytics /> into app/layout.tsx.
  • Pages Router — wrap <Component /> in _app.tsx with <WebalyticsPages />.

The adapter listens for Next's native route changes (usePathname / useSearchParams in App Router, router.events in Pages Router) so pageviews never double-fire from the core tracker's History API patching.

Install

npm install @jlaviole90/tracker @jlaviole90/tracker-next

App Router

// app/layout.tsx
import { Webalytics } from "@jlaviole90/tracker-next";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html>
      <body>
        {children}
        <Webalytics
          siteId={process.env.NEXT_PUBLIC_WEBALYTICS_SITE_ID!}
          host={process.env.NEXT_PUBLIC_WEBALYTICS_HOST!}
        />
      </body>
    </html>
  );
}

<Webalytics /> is already wrapped in a <Suspense> boundary internally, so static prerender works without you adding one.

Custom events

"use client";
import { getTracker, useWebalytics } from "@jlaviole90/tracker-next";

export function SignupButton() {
  return <button onClick={() => getTracker().track("signup", { plan: "pro" })}>Sign up</button>;
}

useWebalytics() returns the same instance; useful inside deep component subtrees.

Pages Router

// pages/_app.tsx
import { WebalyticsPages } from "@jlaviole90/tracker-next/pages";

export default function App({ Component, pageProps }) {
  return (
    <>
      <WebalyticsPages
        siteId={process.env.NEXT_PUBLIC_WEBALYTICS_SITE_ID!}
        host={process.env.NEXT_PUBLIC_WEBALYTICS_HOST!}
      />
      <Component {...pageProps} />
    </>
  );
}

Env

If siteId / host aren't passed as props, the adapter reads:

  • NEXT_PUBLIC_WEBALYTICS_SITE_ID
  • NEXT_PUBLIC_WEBALYTICS_HOST

These are inlined at build time by Next, so they must be available during next build.