fix: pass in full pathname + search in TSR to avoid trailing slashes

[franky47]

TBC if this method causes problems elsewhere (maybe running loaders when not needed?)

Also fixes persistence of custom history.state properties.

Closes #1215.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
nuqs	Ready	Preview	Comment	Nov 21, 2025 10:33am

[pkg-pr-new]

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

commit: d4694dd

[SeanCassiere]

The removal of from should be fine, since Tanner made some changes in router-core, during the big devinxi rewrite, to do more inference of the from value in router.buildLocation.

Its definitely weird that it is busting through the default of never for the trailingSlash option.

---

On the testing side of things, I'd make sure that your e2e testing covers the Router running at.

1. At the apex - localhost:3000?foo=bar
2. On a subpath - localhost:3000/basepath?foo=bar
3. Using hash routing - localhost:3000/#/?foo=bar

This testing might even make sense to be applied to the other adapters.

[SeanCassiere]

You might want to pull the pathname out using useLocation. I'd use a selector in there, for fine-grained subscriptions.

[franky47]

Thanks for your review @SeanCassiere (and good luck with the move!) 🫶

I doesn't work on the apex route indeed, and even this causes TSR to emit a trailing slash:

navigate({ href: 'https://example.com?foo=bar' })
// navigates to https://example.com/?foo=bar

I'll look into the TSR code to see if this can be fixed upstream, even if we're not following the intended use of the API, trailingSlash should be respected.

Edit: actually it doesn't seem possible to not have a trailing slash for the apex, even this adds one:

history.replaceState(null, '', 'https://example.com?foo=bar')
// navigates to https://example.com/?foo=bar

[andreastande]

Edit: actually it doesn't seem possible to not have a trailing slash for the apex, even this adds one:

Weird, do you think that is a bug with TSR? Should be possible

[github-actions]

🎉 This PR is included in version 2.8.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[franky47]

Weird, do you think that is a bug with TSR? Should be possible

No, this happens on https://example.com if you type history.replaceState(null, '', 'https://example.com?foo=bar'), so it's not related to any framework, it's a limitation of the web platform.

Actually even loading https://example.com?foo=bar in the browser gives you https://example.com/?foo=bar

[andreastande]

TIL