Skip to content
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

fix(deps): update dependency nuqs to v2 #905

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 24, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nuqs (source) ^1.17.4 -> ^2.0.0 age adoption passing confidence

Release Notes

47ng/nuqs (nuqs)

v2.2.3

Compare Source

Bug Fixes

v2.2.2

Compare Source

Bug Fixes

v2.2.1

Compare Source

Bug Fixes

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
  • parseAsJson now requires a runtime validation function (53a37d4)
chore
Features
  • Add adapter for One (a56aa11)
  • Add custom adapters API (unstable) (3ef698f)
  • Add React Router adapter (cb30a20)
  • Add Remix adapter (4ae6c81)
  • Add vanilla React adapter sandbox (e603a4d)
  • Introducing adapters for other frameworks (a101370), closes #​603 #​620
  • Provide specialised adapters for both Next.js routers (ac95384)
  • Render pretty URLs in other adapters (6618f45)
BREAKING CHANGES
  • Pass in a validation function like a Zod schema parse function
    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.
  • When using Next.js, nuqs v2 requires next@>=14.2.0.
  • nuqs now requires wrapping your app
    with a NuqsAdapter, which is a context provider connecting
    your framework APIs to the hooks' internals.
  • The startTransition option no longer
    automatically sets shallow: false. The Options type
    is no longer generic.
  • The "use client" directive was not included
    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:
Error: Attempted to call withDefault() from the server but withDefault is on
the client. It's not possible to invoke a client function from the server, it can
only be rendered as a Component or passed to props of a Client
Component.

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 requiring
a 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).

  • export path has been renamed. Contents are identical.

Since the /parsers export contained the server cache,
this name makes better sense and helps outline the client/server
nature of features in nuqs.

  • package is now only updating on the nuqs name.

The debugging printouts no longer check for next-usequerystate, only nuqs.

  • the following deprecated APIs have been removed:
  • queryTypes bag of parsers -> use individual parseAsXYZ parsers
    for better tree-shakeability.
  • subscribeToQueryUpdates helper -> since Next.js 14.0.5,
    useSearchParams is reactive to shallow search params updates
  • drop CJS support.

Since 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/nuqs-2.x branch 30 times, most recently from eafe511 to 0e4de20 Compare October 31, 2024 11:29
@renovate renovate bot force-pushed the renovate/nuqs-2.x branch 28 times, most recently from 037cafb to f4c5546 Compare January 20, 2025 02:06
@renovate renovate bot force-pushed the renovate/nuqs-2.x branch from f4c5546 to ea5b262 Compare January 20, 2025 05:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant