Kwan Jun Wen

> Hey @junwen-k any update on this? I'm curious if you found out the issue. Hi, thank you for following up. As mentioned [earlier](https://github.com/molefrog/wouter/issues/393#issuecomment-1852129867), I've actually found out a solution...

I have yet to include any documentation in the README though. But feel free to take a look at the implementation details first before we proceed to documentation.

I think I will make the changes required after resolving https://github.com/molefrog/wouter/issues/393 first. I might also remove the `useMemo` as well. Thanks @molefrog

@molefrog Hi, any chance to see `searchParams` officially supported in this library? Related PR https://github.com/molefrog/wouter/pull/422 :)

I've written the `useSearchParams` function based on [react-router's implementation](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/index.tsx) for `wouter`. The API is similar if not identical to react-router's [useSearchParams](https://reactrouter.com/en/main/hooks/use-search-params) version. So far it has been working great for...

I've created a PR for this feature based on my understanding (I am no expert in Routing 👀). Any feedbacks are welcomed! @molefrog

> i find it quite often that you might want to replace searchParam but you don't really want to trigger a re-render in same component! > > useSearch will trigger...

> > This is fixed in #324. You can now style with the default key, those styles will be overidden by any type specific ones. > > Just a heads...