Post

Waku now supports search params typing (opt-in), like TanStack Router has done before. Both give you typed search, but their coding styles are different, as the requirement is different. Waku: a typed prop from a codec you provide. TanStack: validateSearch + useSearch.

1 repost13 likes

Does the codec approach in Waku let you reuse the same validation logic across client and server, or do you end up defining search param types separately on each side?