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

@a11yst/source-mapping-next

v1.0.2

Published

Conservative Next.js static route catalog and source mapping for a11yst

Readme

@a11yst/source-mapping-next NPM version License: MPL-2.0 NPM total downloads

Conservative static Next.js route catalog and source mapping for a11yst Phase 10e.

Scope

This package consumes @a11yst/source-index and @a11yst/source-mapping-react to:

  • Detect App Router roots (app/, src/app/) and Pages Router roots (pages/, src/pages/)
  • Build a static route catalog from indexed filenames only
  • Narrow React catalog files by matched route, router, scope, and optional hints
  • Delegate element matching to mapReactSource()
  • Enrich candidates with Next.js metadata

Supported:

  • Static, dynamic, catch-all, and optional catch-all route patterns
  • App Router route groups, layouts, templates, and state files in the catalog
  • Pages Router _app, _document, _error, and special error pages
  • Client/server module boundary hints for App Router files
  • Conservative ambiguity when multiple files or routers match

Not supported in 10e:

  • Reading .next build output or manifests
  • Executing Next.js or evaluating runtime navigation
  • Rewrites, redirects, middleware, basePath, or i18n routing
  • Custom pageExtensions from next.config.*
  • Route handlers and API routes as UI sources
  • Intercepting routes in automatic matching
  • Parallel routes without an explicit slot hint
  • Import resolution, source maps, ranking, recommendations, or audit integration

Phase 10f adds Vue/Nuxt. Phase 10h adds ranking. Phase 10i adds recommendations.

Route narrowing

Route evidence reduces the React search space. It never creates a candidate by itself and never upgrades confidence to exact.

Unique selector matches inside the narrowed file set keep React confidence rules (high for unique selectors, never exact except existing source locations).

When the same selector appears in both a layout and a page, the result is ambiguous with no selected candidate.

Security

The catalog and mapping never store source code, AST nodes, concrete route parameter values, query strings, hash fragments, absolute paths, or secrets.

Public API

  • createNextRouteCatalog()
  • mapNextSource()
  • normalizeNextRoutePath()
  • resolveRoutesForPath()
  • stableSerializeNextCatalog()