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

@multitenant/next-app

v0.5.1

Published

Next.js **App Router** integration for `@multitenant/core`.

Readme

@multitenant/next-app

Next.js App Router integration for @multitenant/core.

It provides:

  • createTenantMiddleware(registry, options) – Next.js middleware.ts factory
  • createTenantMiddlewareFromConfig(config, options)from @multitenant/next-app/auto when you already have a loaded TenantsConfig object
  • createNodeTenantMiddlewareFromProjectRoot(options?)from @multitenant/next-app/auto-node (Node only): loads ./tenants.config.json from process.cwd() via @multitenant/config
  • getTenantFromHeaders(headers, registry, options?) – read ResolvedTenant in route handlers / server components
  • requireTenant(headers, registry, options?) – same but throws if missing

Runtime: auto-node uses fs and must not run on Edge. Use auto with a static import or bundled JSON if middleware must run on Edge.

Install

npm install @multitenant/next-app @multitenant/core

Usage

middleware.ts

import type { EnvironmentName } from '@multitenant/core';
import { createTenantMiddleware } from '@multitenant/next-app';
import tenantsConfig from './tenants.config.json';
import { createTenantRegistry } from '@multitenant/core';

const registry = createTenantRegistry(tenantsConfig as any);
const env = (process.env.TENANT_ENV ?? 'local') as EnvironmentName;

export const middleware = createTenantMiddleware(registry, {
  environment: env,
});

Missing tenant behavior

createTenantMiddleware resolves the tenant from the incoming request Host header (it also respects x-forwarded-host). If the current host doesn't match any tenant domain (common when you run next dev directly on localhost instead of via multitenant dev), tenant resolution will fail. By default (onMissingTenant: 'passthrough') the middleware will not throw; it will NextResponse.next() (no tenant headers are added). Your app/server code must still handle getTenantFromHeaders(...) === null if you don’t route through multitenant dev. If you want a hard failure (or logs), set onMissingTenant: 'throw' (or 'warn').

In route handlers / server components

import { headers } from 'next/headers';
import { getTenantFromHeaders } from '@multitenant/next-app';
import { tenantRegistry } from './tenant-registry';

export async function GET() {
  const h = headers();
  const tenant = getTenantFromHeaders(h, tenantRegistry, { environment: 'local' });
  // ...
}

Full App Router checklist: next-app-router.md.


Open source

MIT licensed — github.com/klypalskyi/multitenant · Issues · npm