feat: Add support for TanStack Router

[ahmedrowaihi]

No description provided.

[vercel]

@ahmedrowaihi is attempting to deploy a commit to the 47ng Team on Vercel.

A member of the Team first needs to authorize it.

[ahmedrowaihi]

the nuqs DX is unbeatable, let's make it work everywhere

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	54.5 kB	ljharb
npm/[email protected]	None	0	11.3 kB	sindresorhus
npm/[email protected]	None	+5	73.5 kB	silvenon

🚮 Removed packages: npm/@sentry/[email protected], npm/@shikijs/[email protected], npm/@size-limit/[email protected], npm/@t3-oss/[email protected], npm/@tailwindcss/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@testing-library/[email protected], npm/@tremor/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@vitejs/[email protected], npm/@vitest/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

[franky47]

Thank you for this! 🙌

I see the adapter is based on the next/app one, have you tried it in a TSR app? My main concern would be shallow routing support.

Also, you'll need to add the new entry points to the files list in package.json (otherwise they won't land on NPM).

[ahmedrowaihi]

@franky47

I see the adapter is based on the next/app one, have you tried it in a TSR app? My main concern would be shallow routing support.

Yes, I am using it on my TSR app, it's doing the thing pretty good
the shallowing is not doing different effect for now since the app is SPA, and it's just doing optimistic set

Also, you'll need to add the new entry points to the files list in package.json (otherwise they won't land on NPM).

updated

[ahmedrowaihi]

oh wait, I just found a bug when shallow is true xD
let me fix it

[ahmedrowaihi]

@franky47 I fixed it, I reused the TSR router to navigate and this is working now

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nuqs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2025 9:10pm

[franky47]

Thanks, I took the liberty of flattening the TSR adapter code, the impl file was mostly needed for Next.js to have the agnostic adapter pull out implementations from both app & pages adapters.

Looks good for a start, since TSR is mostly for SPAs, I'll add an e2e test environment on this PR tomorrow to see how it behaves. Then there's the question of how to handle the shallow: false option in TanStack Start for SSR, but we can deal with that later.

[pkg-pr-new]

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

commit: 1e22fbc

[franky47]

The initial porting of the shared e2e test suite looks pretty good!

This is likely to be only the tip of the iceberg though, the real value in a TSR adapter would be to connect nuqs search params definition objects (the ones you feed to useQueryStates, create{Loader,Serializer} etc) to TSR's route definitions for seamless integration with type-safe routing (getting nuqs' search params in TSR's <Link> components, and having it use custom serialisation in the URL when doing so).