feat: Add temporary dedicated server features imports #805
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 allows using the serializer and the parsers in server-side code without depending on React for the cache, as would be the case if importing from
nuqs/server
.🦋 https://bsky.app/profile/francoisbest.com/post/3ld5bqxov722z
X: https://x.com/nuqs47ng/status/1867331081349083400
Tasks
moduleResolution
Note
This PR adds three new imports:
nuqs/server/cache
: exports only the cache feature. Requires React canary (currently only useful in Next.js app router)nuqs/server/parsers
: exports defs & all built-in parsersnuqs/server/serializer
: exports defs & thecreateSerializer
featureThe
nuqs/server
import is untouched in this PR.Future breaking change plans
In nuqs v3:
nuqs/server/cache
will be the only way to import the cache feature, it will be removed fromnuqs/server
nuqs/server/parsers
andnuqs/server/serializers
may be removed for cleanup, as their code will be importable fromnuqs/server
in a framework-agnostic way.Closes #804.
See also discussion #717.