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

@usevane/next

v0.1.7

Published

Next.js adapter for Vane. Proxy middleware, custom signal API, and instrumentation hook.

Readme

@usevane/next

Next.js adapter for Vane. Proxy middleware, custom signal API, and instrumentation hook.

bun add @usevane/next

Requires next >= 15.0.0 as a peer dependency.

Setup

1. Environment

VANE_API_KEY=proj_xxx

2. Middleware proxy

Create or update your middleware to capture traffic signals on every request. The proxy never blocks responses -- it ships signals via waitUntil and fails open on any error.

// middleware.ts
import { createProxy } from '@usevane/next'

export default createProxy()

export const config = {
  matcher: ['/((?!_next/static|_next/image|favicon.ico).*)'],
}

3. Instrumentation (optional)

Warm the config cache on server startup so the first request skips the fetch.

// instrumentation.ts
export { register } from '@usevane/next/instrumentation'

Custom signals

Send domain-specific events that bypass sampling. Resolves when queued (<1ms) -- does not wait for Redis confirmation.

import { vane } from '@usevane/next'

await vane.signal('clickthrough', { entity: '/pricing' })
await vane.signal('checkout', { entity: '/cart', amount: 99 })

Exports

| Entrypoint | Export | Description | |:-----------|:-------|:------------| | @usevane/next | createProxy | Middleware factory -- captures traffic signals | | @usevane/next | vane | Custom signal API (vane.signal()) | | @usevane/next | createVercelAdapter | Low-level Vercel platform adapter | | @usevane/next/instrumentation | register | Next.js instrumentation hook |

Constraints

  • Edge-runtime compatible. No Node.js APIs.
  • next is a peer dependency -- never bundled.
  • Always fails open. Signal capture errors never break your app.

Docs

https://vane.moe/docs

License

MIT