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

@redactenv/next

v0.1.0

Published

Next.js adapter for redactenv: instrumentation hook + Response wrapper + error scrubbing

Readme

@redactenv/next

Next.js adapter. Two entry points: global Response patcher (via instrumentation.ts) and a middleware helper.

npm install @redactenv/next @redactenv/patterns

Zero-config (recommended)

Create instrumentation.ts at the project root:

export async function register() {
  if (process.env.NEXT_RUNTIME === 'nodejs') {
    await import('@redactenv/next/auto');
  }
}

That's it. Boot log shows what's protected. Default profile = env snapshot (with sensible allowlist that skips NODE_ENV, PORT, NEXT_PUBLIC_*, VERCEL_*, AWS_REGION, …) + every confidence: 'high' pattern.

Need overrides? Use Option 1 below.


Option 1: instrumentation hook with custom config

Patches the global Response constructor at boot. Every Response and Response.json() returned from a route handler or page is scanned.

// instrumentation.ts (project root or src/)
export async function register() {
  if (process.env.NEXT_RUNTIME === 'nodejs') {
    const { installNext } = await import('@redactenv/next');
    const { highConfidencePatterns } = await import('@redactenv/patterns');

    installNext({
      rules: [
        { name: 'env', source: 'process.env', action: 'redact' },
        ...highConfidencePatterns.map(p => ({ ...p, action: 'hash' as const })),
      ],
      allowEnvKeys: ['NEXT_PUBLIC_*', 'NODE_ENV'],
    });
  }
}

Enable instrumentation in next.config.js:

module.exports = { experimental: { instrumentationHook: true } };

(Next 15+: no flag needed.)

Option 2: middleware helper

For per-route or middleware.ts use:

// middleware.ts
import { createMiddleware } from '@redactenv/next/middleware';

const redact = createMiddleware({
  rules: [{ name: 'env', source: 'process.env' }],
});

export async function middleware(req: Request) {
  return redact(req, async () => fetch(req));
}

Options

interface InstallOptions extends RedactorConfig {
  redactor?: Redactor;          // reuse existing redactor
  redactHeaders?: boolean;      // default true
  redactBody?: boolean;         // default true
  contentTypes?: RegExp;        // which content-types to scan; default JSON/text/XML/SVG
}

Caveats

  • Edge runtime: current build uses node:crypto. For Edge, instantiate redactor without env rule, or wait for Edge variant in 0.2.
  • Streams: installNext scans string BodyInit only. ReadableStream bodies pass through unchanged in 0.1.x.
  • Response.error() / Response.redirect() pass through (no body).

License: MIT