chore: add Knip for upkeeping

[franky47]

• [x] Enable test coverage
• [x] Remove unused dependencies
• [x] Refactor some internals
• [x] Export CreateStandardSchemaV1Options type
• [x] Run knip in CI (needs all deps, maybe move it to its own job)
• [ ] Enable knip for docs
• [ ] Enable knip for e2e tests
• [ ] Enable knip for examples

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
nuqs	Skipped			Nov 21, 2025 0:40am

[pkg-pr-new[bot]]

pnpm add https://pkg.pr.new/nuqs@1154

commit: c0796d3

[franky47]

@webpro I get a failure when running knip in CI (and can reproduce locally) with the following conditions:

• I install only the --workspace-root dependencies (where knip is defined)
• I run pnpm run lint:knip --workspace packages/nuqs to only check the nuqs package
• It fails when trying to load something unrelated in the e2e environments:

$ pnpm run lint:knip --workspace packages/nuqs

> [email protected] lint:knip /Users/franky/dev/playground/47ng/nuqs
> knip --workspace packages/nuqs

ERROR: Error loading /Users/franky/dev/playground/47ng/nuqs/packages/e2e/react-router/v6/cypress.config.ts
Reason: Cannot find module 'e2e-shared/cypress.config'
Require stack:
- /Users/franky/dev/playground/47ng/nuqs/packages/e2e/react-router/v6/cypress.config.ts
 ELIFECYCLE  Command failed with exit code 2.
zsh: exit 2     pnpm run lint:knip --workspace packages/nuqs

Running pnpm run lint:knip --workspace packages/nuqs works fine if I have all the monorepo dependencies installed (although it takes a bit longer than when I had knip only set up as a dependency of the nuqs package).

Is knip trying to check somewhere it shouldn't?

[webpro]

Thanks for giving Knip a shot! There are two things relevant here:

• When linting a single workspace, Knip includes ancestor and dependent workspaces. For instance, to figure out what exports of the linted workspace are unused. (It might be interesting to look into optimizations here to see exactly what operations could be skipped, but at the moment Knip calculates the relevant workspaces and does its thing on all of 'em and eventually reports only the issues for the provided workspace.)
• Knip is a mostly static analysis tool, but it loads/imports configuration files like cypress.config.ts. That's because, in most cases, we want the resolved exported configuration object to find entry points and dependencies. Some plugins have an (additional) AST resolver, but it's not as common.

The result is that dependencies of at least the ancestors and dependents should be installed upfront.

Does that help?

[franky47]

That makes sense, thanks for the explanation! I'll run knip on a fully-installed dependencies setup then.