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

lanternfish-next

v0.1.0

Published

Lanternfish analytics for Next.js: the tracker tag, an ad-blocker-proof proxy route and AI-agent logging.

Readme

lanternfish-next

Lanternfish for Next.js (App Router, Next 15.1 or later). It does three jobs:

  • adds the tracker to every page;
  • sends events through your own domain, so ad blockers see a first-party request;
  • logs AI agents and crawlers (GPTBot, ClaudeBot, PerplexityBot and others), which never run JavaScript.

You don't need this package to use Lanternfish: one script tag counts visits on any site. Use it when you want the two extras without copying files.

Set up

npm install lanternfish-next

1. Environment variables. Copy them from your site's Settings page in the Lanternfish dashboard:

LF_ORIGIN=https://lanternfish.you.workers.dev
LF_SITE=abc123
LF_SERVER_KEY=...

2. The tracker. In app/layout.tsx:

import { Lanternfish } from "lanternfish-next";

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        {children}
        <Lanternfish />
      </body>
    </html>
  );
}

3. The proxy route. Create app/api/e/route.ts with one line:

export { POST } from "lanternfish-next";

4. AI agents (optional). Create proxy.ts at the project root (middleware.ts on Next 15):

export { proxy } from "lanternfish-next/proxy";
export const config = { matcher: "/((?!_next/|favicon.ico).*)" };

On Next 15, export middleware instead of proxy. Next.js needs config written out in this file, so it can't come from the package. For people it does one user-agent check and lets the request through.

Already have a proxy or middleware? Call logAgent(req) from it instead:

import { logAgent } from "lanternfish-next";

export function proxy(req: NextRequest) {
  logAgent(req);
  // ...your own logic
}

Options

<Lanternfish /> reads LF_ORIGIN and LF_SITE, and renders nothing until both are set. Props override them:

| Prop | Default | |---|---| | origin | LF_ORIGIN | | site | LF_SITE | | api | "/api/e" when LF_SERVER_KEY is set, otherwise events go straight to the Worker. false never proxies. |

Without LF_SERVER_KEY the route and agent logging do nothing, and the tracker talks to the Worker directly.

Licence

AGPL-3.0-only.