-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): update dependency nuqs to v2 #142
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/nuqs-2.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
4 times, most recently
from
October 24, 2024 09:46
05ad9df
to
330ec64
Compare
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
October 30, 2024 16:20
330ec64
to
b4ff5e8
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
October 31, 2024 13:23
b4ff5e8
to
ba67a73
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
4 times, most recently
from
November 14, 2024 17:32
a0eecd3
to
1b3dfa2
Compare
Deployment failed with the following error:
|
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
2 times, most recently
from
November 20, 2024 21:07
b42aad0
to
baa2dc6
Compare
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
November 23, 2024 16:26
baa2dc6
to
24956a5
Compare
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
December 4, 2024 08:05
24956a5
to
d93048a
Compare
Deployment failed with the following error:
|
renovate
bot
changed the title
build(deps): update dependency nuqs to v2
build(deps): update dependency nuqs to v2 - autoclosed
Dec 8, 2024
renovate
bot
changed the title
build(deps): update dependency nuqs to v2 - autoclosed
build(deps): update dependency nuqs to v2
Dec 8, 2024
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
December 8, 2024 21:07
3410117
to
d93048a
Compare
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
January 1, 2025 22:16
d93048a
to
bf654fe
Compare
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
January 14, 2025 18:23
bf654fe
to
c3b880d
Compare
renovate
bot
force-pushed
the
renovate/nuqs-2.x
branch
from
January 16, 2025 08:20
c3b880d
to
6da870f
Compare
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.
This PR contains the following updates:
1.20.0
->2.3.1
Release Notes
47ng/nuqs (nuqs)
v2.3.1
Compare Source
Bug Fixes
Performance Improvements
v2.3.0
Compare Source
Features
Bug Fixes
?
characters in serializer base (#821) (8951598), closes #812 - Thanks @ealvarezk!Nullable
type for correctly inferring return type ofcreateSerializer()
(#801) (ab99d7d) - Thanks @MartinCura!Other changes
New Contributors
Full Changelog: 47ng/nuqs@v2.2.3...v2.3.0
v2.2.3
Compare Source
Bug Fixes
v2.2.2
Compare Source
Bug Fixes
v2.2.1
Compare Source
Bug Fixes
null
value in serializer for parsers with default values (#769) (84c5189) - Thanks @MartinCura!v2.2.0
Compare Source
Features
Bug Fixes
v2.1.2
Compare Source
Bug Fixes
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: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.