use-query-params VS router

With react router v5 I was using a library called use-query-params. It had this great hook called useQueryParam which let you manage 1 query parameter in the same way as useState worked.

I like https://github.com/pbeshai/use-query-params

Nothing is stopping you from storing state in the URL query string params. I do so frequently for pages containing tables where it's important to keep filtering and pagination state in sync with the URL, for example. Use this library https://github.com/pbeshai/use-query-params

Welcome to the first article of a series where we will explore TanStack Router, a new router for React (version 1.0 released in December 2023).

Tanstack - Tanstack has evolved to an entire ecosystem consisting of the famous Tanstack (or React) Query, Tanstack Table, now also Tanstack Router and Tanstack Form. It started with Tanstack Query, which adopted Nx and Nx Cloud. Zack talked about this collab with Dominik, and we also had Dominik on our Nx live stream. Now, all the above-mentioned Tanstack libs have adopted Nx, and there's more coming.

We've found that `tanstack/router` was patched to make HMR work as expected, but this solution doesn't work for us, as our config is not a class: https://github.com/TanStack/router/commit/9f2150190a628fb3767ca8ad0d8634b357f43c51

Start a discussion about what you'd like to see and I'll do my best. https://github.com/tanstack/router/discussions

React Location certainly needs more attention in the React community. React Location also has a grooving community you can find on StackOverflow, Discord, and GitHub discussions. Finally, I invite you all to try out React Location and see how fantastic a routing solution is.

Enterprise Client-Side Routing for React Enjoy this library? Try the entire TanStack! React Query, React Table, React Charts, React Virtual Visit react-location.tanstack.com for docs, guides, API and more!