usehooks-ts VS use-query-params

These depedencies provide unstyled accessible components from headless ui, icons from heroicons and common hooks with typescript support.

🏡 Local Storage - All score history, streaks, and user info is saved in Local Storage! Check out `useLocalStorage` by https://usehooks-ts.com/. A great resource and helpful when you want to quickly manage it like any other state.

We will store last search query string in local storage, thus I will summon useLocalStorage from usehooks-ts:

There are tons of examples of people building hooks for IntersectionObserver, they are probably a good deal more complex than what you want but you can learn a lot from how they do it and then simplify it to your needs, here is one: https://github.com/juliencrn/usehooks-ts/blob/master/src/useIntersectionObserver/useIntersectionObserver.ts

Take a look at Use hooks libraries for examples of code that you may want to have portability with (this is they typescript one because its the one I've used)

One of the simplest examples is "useToggle" which just sets a state variable to true or false. Not hard to write in a class component but it's still stuff that you may end up writing a lot.

A lot of similar ones are click and event handlers that need to be cleaned up after the component is unmounted.

useIsMounted is one I use a lot too to ensure I'm not trying to write state on an API callback once a component is unmounted.

You could add each of these to a class with an hoc and end up with withToggle(withIsMounted(withUseMediaEvent(MyComponent))) but that tends to be a bit of a mess.

https://usehooks-ts.com/

This implementation of the useCopyToClipboard hook comes from the usehooks-ts library. It provides an easy way to copy text to the clipboard. Other React hooks libraries also have this hook which they implement differently: some rely on JavaScript libraries like copy-to-clipboard that run on document.execCommand() while others like this one depend on the clipboard API.

1: usehooks-ts

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