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

@querycn/filter-next

v0.3.0

Published

Next.js App Router bindings for @querycn/filter-react: URL adapter, provider and a server-side filter parser.

Readme

@querycn/filter-next

Next.js App Router bindings for @querycn/filter-react: a URL adapter, a ready-wired provider and parseFilters for server components and route handlers.

pnpm add @querycn/filter-core @querycn/filter-react @querycn/filter-next

Usage

Keep fields in a module without "use client", so both the server page and the client provider can import the real array:

// app/orders/fields.ts
import type { FieldDefinition } from "@querycn/filter-core"

export const fields: FieldDefinition[] = [
  { name: "status", label: "Status", type: "select", options: [/* … */] },
  { name: "amount", label: "Amount", type: "number" },
]

Render the provider from a client component: onApply, loadOptions and serializers are functions and can't be passed from a server component.

// app/orders/orders-filter.tsx
"use client"

import { NextFilterProvider } from "@querycn/filter-next"

import { fields } from "./fields"

export function OrdersFilter({ children }: { children: React.ReactNode }) {
  return (
    <NextFilterProvider fields={fields} onApply={() => ({ page: null })}>
      {children}
    </NextFilterProvider>
  )
}

Read the applied filter on the server:

// app/orders/page.tsx
import { parseFilters } from "@querycn/filter-next/server"

import { fields } from "./fields"

export default async function Page(props: {
  searchParams: Promise<Record<string, string | string[] | undefined>>
}) {
  const filter = parseFilters(await props.searchParams, { fields })
  // query your data with `filter` …
}

In a route handler: parseFilters(request.nextUrl.searchParams, { fields }).

Notes

  • Suspense. useSearchParams makes a statically prerendered route fail next build unless the provider sits inside <Suspense>; the subtree then renders on the client only. Routes that await searchParams are dynamic and don't need it.
  • shallow. useNextAdapter({ shallow: true }) (or <NextFilterProvider shallow>) updates the URL through the History API without a server request — for data filtered on the client. Leave it off when a server component reads searchParams.
  • App Router only.

Credits

Inspired by FilterCN (MIT).

License

MIT