fix: nuqs provider#354
Closed
Desmenez wants to merge 2 commits intosoftnetics:mainfrom
Closed
Conversation
🦋 Changeset detectedLatest commit: 193ace7 The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why did you create this PR
Problem
Collection list UI and related hooks called nuqs directly (useSearch, usePagination, useSort). In a Next.js App Router consumer, those hooks require a valid nuqs adapter boundary. When components render outside that boundary (or before the adapter is available), runtime throws [nuqs] NUQS-404.
Solution
Compatibility / risk
Screenshots / Recordings
Checklist