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

next-query-sync

v1.0.2

Published

A lightweight, type-safe URL search params state manager for Next.js

Readme

next-query-sync

A lightweight, type-safe URL search params state manager for Next.js — built with React 18 Concurrent Mode and production performance in mind.

Features

  • 🔒 Type-safe: TypeScript infers exact output types from your parser schema
  • Batched updates: multiple param changes in one event loop → one history call
  • 🌐 SSR-safe: no crashes on the server (window guard throughout)
  • 🔄 React 18 ready: uses useSyncExternalStore — no UI tearing in Concurrent Mode
  • 📦 Dual package: ships both CJS and ESM builds with .d.ts typings
  • 🪶 Zero runtime deps: only a React 18+ peer dependency

Install

npm install next-query-sync
# or
pnpm add next-query-sync

Quick Start (Next.js App Router)

'use client'
import { useQueryState, parseAsInteger } from 'next-query-sync'
import { Suspense } from 'react'

function ProductList() {
  // Method chaining — preferred style
  const [page, setPage] = useQueryState(
    'page',
    parseAsInteger.withDefault(1),
    { history: 'push' }   // creates browser history entries → Back button works
  )

  return (
    <div>
      <h1>Page: {page}</h1>
      <button onClick={() => setPage(p => p + 1)}>Next →</button>
      <button onClick={() => setPage(p => Math.max(1, p - 1))}>← Prev</button>
    </div>
  )
}

// ⚠️ Next.js App Router: wrap in Suspense when reading URL params
export default function Page() {
  return (
    <Suspense fallback={<p>Loading…</p>}>
      <ProductList />
    </Suspense>
  )
}

API Reference

useQueryState(key, parserOrDefault, options?)

Syncs a single URL search param with React state. Supports four calling styles:

const [value, setValue] = useQueryState(key, parserOrDefault, options?)

| Param | Type | Description | |---|---|---| | key | string | URL search param name | | parserOrDefault | Parser<T> | ParserWithDefault<T> | Primitive | Zod schema | Determines how to parse/serialize the value | | options.history | 'push' \| 'replace' | Default: 'replace' | | options.debounce | number | Debounce URL writes by N ms (optimistic UI while typing) | | options.startTransition | boolean | Wrap URL writes in React.startTransition (non-urgent updates) |

Style 1 — Primitive default (auto-inference, like useState):

const [count, setCount]   = useQueryState('count', 0)      // number, never null
const [search, setSearch] = useQueryState('search', '')    // string, never null
const [active, setActive] = useQueryState('active', false) // boolean, never null

Style 2 — Method chaining (preferred):

const [page, setPage]   = useQueryState('page', parseAsInteger.withDefault(1))
const [date, setDate]   = useQueryState('date', parseAsIsoDateTime.withDefault(new Date()))
const [q, setQ]         = useQueryState('q', parseAsString)  // string | null

Style 3 — Zod schema:

import { z } from 'zod'
const FilterSchema = z.object({
  role:   z.enum(['admin', 'user', 'guest']),
  status: z.enum(['active', 'banned']),
}).default({ role: 'user', status: 'active' })

// Pass the schema directly — no wrapper needed
const [filter, setFilter] = useQueryState('filter', FilterSchema)
// filter: { role: 'admin' | 'user' | 'guest'; status: 'active' | 'banned' }
//         → never null, always validated
// URL: ?filter=%7B%22role%22%3A%22admin%22%7D  (auto JSON-encoded)
// Tampered / invalid URL → silently falls back to .default({...})

setFilter(f => ({ ...f, role: 'admin' }))

Style 4 — Debounce + startTransition (ideal for search inputs):

const [q, setQ] = useQueryState('q', '', { debounce: 300, startTransition: true })

useQueryStates(schema, options?)

Syncs multiple URL params at once. All updates in one setValues call are coalesced into a single URL write.

| Param | Type | Description | |---|---|---| | schema | Record<string, Parser<T>> | Map of key → parser | | options.history | 'push' \| 'replace' | Default: 'replace' |

import { useQueryStates, parseAsString, parseAsInteger, withDefault } from 'next-query-sync'

function ProductFilters() {
  const [filters, setFilters] = useQueryStates(
    {
      sort:   withDefault(parseAsString,  'latest'),
      page:   withDefault(parseAsInteger, 1),
      search: parseAsString,
    },
    { history: 'push' }  // each setFilters() call → one history entry
  )
  // filters.sort   → string        (default: 'latest', never null)
  // filters.page   → number        (default: 1, never null)
  // filters.search → string | null

  // Changing sort resets page — still one history entry:
  const handleSort = (sort: string) => setFilters({ sort, page: 1 })
}

Built-in Parsers

| Parser | URL value | JS value | |---|---|---| | parseAsString | "hello" | "hello" | | parseAsInteger | "42" | 42 | | parseAsFloat | "3.14" | 3.14 | | parseAsBoolean | "true" / "false" | true / false | | parseAsIsoDateTime | "2026-03-16T09:00:00.000Z" | Date | | parseAsArrayOf(p) | "a,b,c" | ["a","b","c"] |

All parsers return null for missing/unparseable values. Chain .withDefault(value) to eliminate null:

// Every built-in parser supports .withDefault()
parseAsString.withDefault('')
parseAsInteger.withDefault(1)
parseAsFloat.withDefault(0.0)
parseAsBoolean.withDefault(false)
parseAsIsoDateTime.withDefault(new Date())
parseAsArrayOf(parseAsString).withDefault([])

// Re-chain to override the default value:
parseAsInteger.withDefault(1).withDefault(99)  // → default is 99

withDefault(parser, defaultValue)

Wraps any parser so that missing/unparseable values return defaultValue instead of null. TypeScript will narrow the return type to T (no null).

Preferred: use the .withDefault() method directly on any parser — it is equivalent and reads better:

// Method chaining (preferred)
const pageParser = parseAsInteger.withDefault(1)

// HOF style (still supported, kept for backward compatibility)
const pageParser = withDefault(parseAsInteger, 1)

// Both are equivalent:
// pageParser.parse(null) → 1
// pageParser.parse('5')  → 5

const [page, setPage] = useQueryState('page', pageParser)
// page: number  ← TypeScript knows this is never null

Custom Parsers

Use makeParser to create a fully-typed parser with .withDefault() support automatically attached:

import { makeParser } from 'next-query-sync'

const parseAsDate = makeParser<Date>(
  (v) => {
    if (!v) return null
    const d = new Date(v)
    return isNaN(d.getTime()) ? null : d
  },
  (d) => d.toISOString().split('T')[0]!
)

// Method chaining works out of the box:
const [date, setDate] = useQueryState('date', parseAsDate.withDefault(new Date()))

Alternatively, implement the Parser<T> interface directly:

import type { Parser } from 'next-query-sync'

const parseAsDate: Parser<Date> = {
  parse: (v) => {
    if (!v) return null
    const d = new Date(v)
    return isNaN(d.getTime()) ? null : d
  },
  serialize: (d) => d.toISOString().split('T')[0]!,
  withDefault: (defaultValue) => ({
    parse: (v) => parseAsDate.parse(v) ?? defaultValue,
    serialize: parseAsDate.serialize,
    withDefault: parseAsDate.withDefault,
    defaultValue,
  }),
}

How It Works

Batching

queueMicrotask is used to defer the actual history.replaceState / history.pushState call. Multiple synchronous updates (e.g. calling setPage(2) and setSearch('react') in the same handler) are merged into one URL write:

Event handler
  setPage(2)      → scheduleUrlUpdate('page', '2')   ─┐ same microtask batch
  setSearch('q')  → scheduleUrlUpdate('search', 'q') ─┘
                                                        ↓
                                             history.replaceState(…?page=2&search=q)

SSR Safety

Every access to window is guarded by typeof window === 'undefined'. useSyncExternalStore's getServerSnapshot always returns null, so the hook renders correctly on the server without hydration mismatches.

React 18 Concurrent Mode

useSyncExternalStore (React 18+) ensures that all components reading the same URL param see a consistent snapshot — no tearing when React interrupts and restarts renders.


License

MIT