Are query params supposed to persist after router.push

[tylersayshi]

Let's say I am on /about?name=foo then I run router.push('/elsewhere') from next's router.

Currently, I am seeing this navigate me to /elsewhere?name=foo... Is this expected? My understanding was that query parameters would only persist if explicitly passed to router.push('/elsewhere' + queryParams).

Am I misunderstanding how this should work?

If my understanding is correct, what might cause nuqs to persist query params across paths?

If I am incorrect, could you recommend a way to clear the query parameters on this router.push event.

Thanks in advance! nuqs is great :)

[tylersayshi]

So I am observing two steps here

1. I call router.push('/elsewhere'). This correctly triggers the navigate event to just /elsewhere
2. a router.replace is triggered by this line here: https://github.com/47ng/nuqs/blob/v1.19.1/packages/nuqs/src/sync.ts#L120

Is this expected behavior and can it be disabled?

[tylersayshi]

as I console.log on navigation.addEventListener('navigate', ...) I see:

1. push to /elsewhere
2. replace from nuqs with query params that were used on /about
3. a replace that removes one of the 4 query params that got copied from the last page (There's no apparent pattern to why this one was removed)
4. The one that was removed in step 3 re-appears & the first calls to setState (from useQueryState) on the new page add two new query param items

This seems like a bug afaict

[franky47]

That's wild indeed. If you're able, could you give v2 a try? The whole sync thing has been removed there (it was only necessary for some unstable versions of Next.js' shallow routing).

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

Docs for migration (only hard requirement if you're not using deprecated things is to be on next@>=14.1.2):
#459

[tylersayshi]

With initial testing - this just works :) Thanks so much for the quick response.

Is there anything I should look out for with using v2 now? Or would you consider it in a fairly stable state that is just waiting on react 19 to be released?

And I didn't notice the Provider requirement you tweeted about yet in the migration notes, I assume that just hasn't been added yet then?

[franky47]

Yeah the adapters PR is a separate one (#644), based on top of v2, but if it's stable enough before Next 15 / React 19 comes out, it'll get merged into v2 and so the main breaking change will be adding the adapters.

[tylersayshi]

Do you think you could publish a v2 alpha or beta version to npm?

[tylersayshi]

Ah, I am actually able to pin to a commit with https://pkg.pr.new/nuqs@97a1ea8

This is good enough for what I'd need, but it might be good to publish v2 to npm before stable just for others to try :) Thanks again!