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

typed-next-router

v0.0.5

Published

Typed helpers for Next.js routing.

Readme

typed-next-router

Typed helpers for Next.js routing.

What It Solves

  • Prevents route path typos at compile time
  • Validates dynamic path params and query keys/values from route metadata

Type-Safe Next.js Surfaces

| Next.js surface | Type safety added | Example | | --- | --- | --- | | next/link (Link) | Restricts href to registered routes and enforces route-specific pathParams/queryParams shape | <Link href={{ path: '/dashboard' }} /> | | next/navigation (useRouter) | Type-checks push/replace/prefetch inputs with the same route contract (path, dynamic params, query keys/values) | router.push({ path: '/users/[id]', pathParams: { id: '42' } }) | | next/navigation (useSearchParams) | Narrows search param key/value types per route via useTypedSearchParams(path) on get/set/append/delete/has | searchParams.set('mode', 'edit') |

Install

npm install typed-next-router

Basic Usage

import { Link, useTypedRouter } from 'typed-next-router';

function Example() {
  const router = useTypedRouter();

  router.push({
    path: '/users/[id]',
    pathParams: { id: '42' },
  });

  return (
    <Link href={{ path: '/dashboard' }}>
      Go dashboard
    </Link>
  );

Route Metadata

// route-map.ts
import type { RouteMapShape } from 'typed-next-router';

export const paramsMap = {
  '/dashboard': {
    queryParams: {
      tab: ['overview', 'alerts'],
      search: [],
    },
  },
  '/users/[id]': {
    pathParams: ['id'],
    queryParams: {
      mode: ['view', 'edit'],
    },
  },
} as const satisfies RouteMapShape;

[] means dynamic string value for that query key.

  • search: [] => search accepts any string
  • mode: ['view', 'edit'] => only 'view' | 'edit'

Module Augmentation

// typed-next-router.generated.d.ts
import 'typed-next-router';

declare module 'typed-next-router' {
  export interface RouteRegistry {
    path: '/dashboard' | '/users/[id]';
    map: typeof import('./route-map').paramsMap;
  }
}

FYI: generating route metadata is easier with path-typegen. and you can change satisfies RouteMapShape to satisfies Partial<RouteMapShape<PathType>>