Daishi Kato

@daishikato.com

React library author, maintaining three state management libraries, Zustand🐻, Jotai👻, Valtio🧙, and React framework, Waku⛩️. Join my Discord server 👉 https://discord.gg/MrQdmzd For more links, visit 👉 https://daishikato.com

⛩️ Excited to announce Waku v1.0.0-beta.7! Waku is the minimal React framework for full-stack apps of any size. We’re nearing the end of the beta phase. Give Waku a try and share your feedback! github.com/wakujs/waku/...

Release v1.0.0-beta.7 · wakujs/waku

This release includes a new prefetch mode for the instant navigation use case. What's Changed chore(deps): update dependencies by @dai-shi in #2176 refactor: router decouple from lib by @dai-shi i...

github.com

Waku's Slice is inspired by Gatsby's Slice. The idea is the same. You define a shared component once, then put a <Slice> placeholder where you want it. It renders once and is reused on every page. Gatsby does this with static HTML at build time. Waku does it with RSC.

BildBild

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.

BildBild

Inspired by Next.js's Instant Navigations, Waku now does it partially too. Click between /post/1 and /post/2. Shell and placeholder stay instant, the body streams after the fetch. Next: automatic, one file. Waku: opt-in, two files, since it doesn't want to rely on a compiler.

BildBild

Unlike Next.js, Waku's core doesn't provide a caching mechanism, only static/dynamic rendering. Caching is provided by a separate package, waku-cache. Here's a comparison of cache usage between Next.js and Waku.

BildBild