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

@cairnkit/next

v0.12.4

Published

Next.js router adapters for cairnkit (App Router and Pages Router).

Readme

@cairnkit/next

Next.js router adapters for cairnkit, so a tour can move a reader between routes and pick up where it left off.

cairnkit's engine never imports a router. It asks the host how to read the current path and how to navigate, and this package answers that for Next. If you are not on Next, you write those two functions yourself and skip this entirely.

npm i @cairnkit/core @cairnkit/react @cairnkit/next

App Router

"use client";
import { CairnProvider } from "@cairnkit/react";
import { useAppRouterAdapter } from "@cairnkit/next";

export function CairnRuntime({ children }: { children: React.ReactNode }) {
  return (
    <CairnProvider flows={flows} router={useAppRouterAdapter()}>
      {children}
    </CairnProvider>
  );
}

The provider has to wrap your app rather than sit beside it, so mount it inside <body> in app/layout.tsx.

Pages Router

import { usePagesRouterAdapter } from "@cairnkit/next";

<CairnProvider flows={flows} router={usePagesRouterAdapter()}>
  <Component {...pageProps} />
</CairnProvider>;

API

| Export | Use | | ------------------------- | ------------------------------------------------------ | | useAppRouterAdapter() | App Router. Preferred. | | usePagesRouterAdapter() | Pages Router. | | appRouterAdapter() | Non-hook form, kept for callers that cannot use a hook. |

Prefer the hook forms. appRouterAdapter() calls useRouter inside navigate rather than at the top, which works but breaks the rules of hooks, so it exists for the awkward cases rather than as the default.

Two things worth knowing

Search params are not read. ?tour= deep linking is opt-in through useTourDeepLink, because useSearchParams opts its whole subtree out of prerendering and that is not a cost to impose on every app that mounts a tour.

App Router updates usePathname after the outgoing route's DOM is gone. The engine restarts its missing-anchor timeout on a pathname change for exactly this reason; without it a slow transition would trip the timeout mid-navigation and end the tour on a route it was only passing through.

Full documentation: cairnkit.dev

MIT