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

@kikirrin/livedev-next

v0.9.0

Published

Point-and-prompt development overlay for Next.js — click any element, describe a change, create a GitHub issue

Readme

@kikirrin/livedev-next

Point-and-prompt development overlay for Next.js. Click any element, describe a change in plain language, and livedev creates a labelled GitHub issue against your project repo.

What's new in 0.8.0

Breaking change — whitelist gating. The overlay now requires:

  1. An OverlayLoader userId={...} prop (the consumer app's session identifier — email, user id, whatever you already use).
  2. A livedev.whitelist.json file at your app root listing allowed user identifiers.

Without both, the overlay will not render (fail-closed). See Migration from 0.7.x below.

Quick start

pnpm add @kikirrin/livedev-next
npx livedev init
  1. next.config.* — wrap with withLiveDev:

    const withLiveDev = require("@kikirrin/livedev-next/webpack");
    module.exports = withLiveDev({ reactStrictMode: true });
  2. app/layout.tsx — mount behind your admin guard:

    import { getSession } from "@/lib/auth";
    import { OverlayLoader } from "@kikirrin/livedev-next";
    
    export default async function RootLayout({ children }) {
      const session = await getSession();
      const isAdmin = session?.user?.role === "ADMIN";
      return (
        <html><body>
          {children}
          {isAdmin && <OverlayLoader userId={session.user.email} />}
        </body></html>
      );
    }
  3. livedev.whitelist.json at your app root:

    { "allowedUsers": ["[email protected]"] }
  4. .env.localNEXT_PUBLIC_GITHUB_TOKEN (PAT with issues:write) and NEXT_PUBLIC_GITHUB_REPO=owner/repo.

  5. pnpm dev → sign in as an admin whose email is in the whitelist → click any component.

Access model

  • The GitHub PAT is the app's shared service credential. It authorises issue creation; it does not identify the caller.
  • The caller is identified by your app's session, passed via userId.
  • Two independent gates: your admin guard decides whether to render <OverlayLoader> at all, and livedev re-checks userId against the whitelist.

Migration from 0.7.x

| 0.7.x | 0.8.0 | |---|---| | <OverlayLoader /> (no props required) | <OverlayLoader userId={...} /> required to load | | No whitelist; anyone with the app could create issues | livedev.whitelist.json with allowedUsers required; fail-closed if missing/empty | | withLiveDev only injected source-location loader | Also inlines the whitelist as NEXT_PUBLIC_LIVEDEV_WHITELIST (so withLiveDev is now required, not just recommended) |

To upgrade: add a livedev.whitelist.json, pass userId from your session to OverlayLoader, and make sure next.config.* uses withLiveDev.

Subpath exports

  • @kikirrin/livedev-next — client-safe: OverlayLoader, isAllowed, Whitelist type.
  • @kikirrin/livedev-next/server — Node-only: loadWhitelist, isAllowed (for server-side gates / proxy backends).
  • @kikirrin/livedev-next/webpack — the withLiveDev Next.js config wrapper.

Further reading

License

MIT