use-query-params VS constate

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

Another one I like is https://github.com/diegohaz/constate, also <100 lines, but it makes contexts much easier to use. FB also uses mostly contexts for state management.

Github

constate - React Context + State

Constate hook provides lifting local state to React Context Level. So you can access/update state variables anywhere in the application with few lines of code. This is useful when you use the same state in multiple components. For example, you have Themes, Colors, Fonts used in multiple components, Users are allowed to change at one place and it should be reflected in the whole application. Package written in TypeScript and very compact.