feat: add nuqs-presets pattern hooks to registry

[iHiteshAgrawal]

Adds 7 production-ready pattern hooks for common URL state patterns:

• use-pagination: Complete pagination with page size control
• use-search: Debounced search with validation
• use-sorting: Multi-column sorting with smart toggling
• use-filters: Type-safe multi-filter management
• use-multi-select: Array-based multi-selection
• use-tabs: Type-safe tab navigation
• use-date-range: Date range selection with presets

All hooks maintained at: https://github.com/iHiteshAgrawal/nuqs-presets

[vercel]

@iHiteshAgrawal is attempting to deploy a commit to the 47ng Team on Vercel.

A member of the Team first needs to authorize it.

[franky47]

This is awesome, thanks! 🙌

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
nuqs	Ready	Preview	Comment	Nov 17, 2025 7:57pm

[iHiteshAgrawal]

resolved all. ready for review again.

[franky47]

One issue I see with the way the files are laid out is that installing multiple hooks will overwrite each other (eg: ~/hooks/types/index.ts), even though the contents are identical.

Overall, each hook should be a single file, and avoid installing multiple levels of barrel files which bring little value to the person adding it in their codebase.

We could also prefix them with the project name to avoid conflicts with possible existing userland hooks, eg ~/hooks/nuqs-presets/useFilters.ts.

Anothing thing that makes nuqs' declarative model interesting is deriving other features from parser declarations (eg: loaders for server-side, serializer to generate href strings for links etc). I need to look into how it's structured in your repo, but having those exports would be good to allow composing those definitions in userland.

[iHiteshAgrawal]

One issue I see with the way the files are laid out is that installing multiple hooks will overwrite each other (eg: ~/hooks/types/index.ts), even though the contents are identical.

Overall, each hook should be a single file, and avoid installing multiple levels of barrel files which bring little value to the person adding it in their codebase.

We could also prefix them with the project name to avoid conflicts with possible existing userland hooks, eg ~/hooks/nuqs-presets/useFilters.ts.

Anothing thing that makes nuqs' declarative model interesting is deriving other features from parser declarations (eg: loaders for server-side, serializer to generate href strings for links etc). I need to look into how it's structured in your repo, but having those exports would be good to allow composing those definitions in userland.

Hey. I've updated the registry to address the feedback. Every hook is now a single file and self-contained.