fix(deps): update dependency nuqs to v2 #6957
Open
+18
−9
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.
This PR contains the following updates:
1.20.0
->2.1.1
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
47ng/nuqs (nuqs)
v2.1.1
Compare Source
Bug Fixes
v2.1.0
Compare Source
Bug Fixes
Features
v2.0.4
Compare Source
Bug Fixes
v2.0.3
Compare Source
Bug Fixes
v2.0.2
Compare Source
Bug Fixes
v2.0.1
Compare Source
Bug Fixes
v2.0.0
Compare Source
Bug Fixes
chore
nuqs/parsers
tonuqs/server
(b6bdc66)Features
BREAKING CHANGES
to validate at runtime and infer the type of the returned data.
UseQueryStatesOptions
is now generic over the key map(the object containing parser definitions you pass to useQueryStates),
and is now a type rather than an interface.
with a NuqsAdapter, which is a context provider connecting
your framework APIs to the hooks' internals.
startTransition
option no longerautomatically sets
shallow: false
. TheOptions
typeis no longer generic.
in the client import (
import {} from 'nuqs'
). It has now been added,meaning that server-side code needs to import from
nuqs/server
to avoid errors like:
Due to a bug in the implementation of shallow routing (WHS),
14.0.3 required a special case for syncing
against external navigation.
In
[email protected]
, we're cleaning this up and requiringa version of Next.js with bug-free support for
shallow routing (with or without experimental WHS
in 14.0.4, and with stabilised WHS in 14.0.5 onwards).
Since the
/parsers
export contained the server cache,this name makes better sense and helps outline the client/server
nature of features in nuqs.
nuqs
name.The debugging printouts no longer check for next-usequerystate, only nuqs.
queryTypes
bag of parsers -> use individualparseAsXYZ
parsersfor better tree-shakeability.
subscribeToQueryUpdates
helper -> since Next.js 14.0.5,useSearchParams
is reactive to shallow search params updatesSince Next has ESM support since v12, it should not really be a breaking change for most.
Big thanks to @andreisocaciu, @tordans, @prasannamestha, @Talent30, @neefrehman, @chbg, @dopry, @weisisheng, @hugotiger, @iuriizaporozhets, @rikbrown, @mateogianolio, @timheerwagen, @psdmsft, and @psdewar for helping !
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.