nuqs state not updating correctly when using Next.js cacheComponents=true

[rajput-hemant]

Hi 👋
I’m running into an issue with nuqs where the URL state seems to stay stale when cacheComponents: true is enabled in next.config.js.

Context

I have a task list → task edit flow where:

• The selected taskId is stored in the URL using nuqs
• When clicking Edit, I navigate to a task form page
• The form is prefilled based on the taskId from nuqs state

This works fine until a previously edited task is deleted.

Problem

When cacheComponents: true is enabled:

• nuqs continues to return the previous taskId
• Even after navigating back to the list and selecting a different task
• This causes the app to try fetching a deleted task, resulting in an error

This behavior does not occur when cacheComponents is disabled.

I’m not sure if this is:

• A bug in nuqs
• An interaction issue with Next.js component caching
• Or expected behavior, and I need to explicitly opt out of caching nuqs state

---

Expected behavior

• nuqs state should reflect the latest URL param
• When navigating back and selecting a new task, the old taskId should not be reused
• Deleting a task should not cause stale URL state to persist

---

Actual behavior

• nuqs returns a stale taskId
• App attempts to fetch a task that no longer exists
• This only happens when cacheComponents: true is enabled

---

Steps to reproduce

1. Enable cacheComponents: true in next.config.js

2. Open the task list page

3. Click Edit on Task A

   • You are navigated to the edit form
   • Form is prefilled correctly
   • nuqs state contains taskId = A

4. Navigate back to the task list

5. Delete Task A

6. Click Edit on Task B

7. ❌ App still reads taskId = A from nuqs

8. ❌ Fetch fails because Task A no longer exists

---

Reproduction sandbox

I’ve created a minimal CodeSandbox with everything needed to reproduce the issue:

👉 https://codesandbox.io/p/devbox/32lkt4

---

Questions

1. Is this behavior expected when using cacheComponents: true?

2. If yes, what’s the recommended way to:

   • Opt out of this caching for nuqs state?
   • Or force nuqs to always sync with the latest URL params?

3. If not expected, I’m happy to raise an issue.

Thanks in advance 🙏
Appreciate all the work on nuqs — it’s been great otherwise!

Screen.Recording.2025-12-22.at.9.43.34.PM.mov

[franky47]

Note: I've escalated this as issue #1273, let's move the discussion there.