v1.0.0-alpha.5

This version introduces a new implementation of Waku Router. While the API remains unchanged, there may be slight differences in behavior. If you notice any issues or unexpected behavior, please report them.

This release also includes several bug fixes.

What's Changed

• refactor(router): refactor router/client by @dai-shi in #1954
• fix(router/client): warn some usages and fix notfound and redirect behaviors by @dai-shi in #1956
• fix(adapters/cloudflare): fix build without cloudflare vite plugin by @dai-shi in #1958
• fix(router/client): improve scroll behavior by @dai-shi in #1959
• feat(router): support types for query and hash update links by @tylersayshi in #1960
• fix: eliminate limitation of rsc path ending with _ by @dai-shi in #1962
• fix(adapters/cloudflare): follow-up fixing build without cloudflare vite plugin by @dai-shi in #1965
• refactor(router): refactor router/client by @dai-shi in #1961
• fix(router): literal route prioritized over slug by @tylersayshi in #1970
• refactor(router): redesign router/client implementation by @dai-shi in #1969

Full Changelog: v1.0.0-alpha.4...v1.0.0-alpha.5

v1.0.0-alpha.4

This release includes various fixes and improvements. Most notably, the Cloudflare adapter has been updated to work with @cloudflare/vite-plugin. It's still fairly new, and Cloudflare users are highly encouraged to try it out and share feedback.

Migration Guide

If you are using Cloudflare Workers for deployment, there is a breaking change to the main entry point. Update your wrangler.jsonc like this:

-   "main": "./dist/server/serve-cloudflare.js",
+   "main": "./src/waku.server",

What's Changed

• fix: netlify build enhancer path config by @yunho1017 in #1931
• chore: use hono/tiny preset by @Master-Hash in #1928
• breaking: avoid decodeURI internally by @dai-shi in #1939
• fix(router): inconsistent URI encoded path between SSR and client by @Master-Hash in #1910
• update vitejs/plugin-rsc by @dai-shi in #1941
• feat(router): typed api request handling as a utility by @tylersayshi in #1938
• feat(cli): restart Waku dev server on Vite server restart by @yunho1017 in #1929
• refactor: rename type file by @dai-shi in #1945
• fix(internals): expose unstable_resolveConfig separating adapter builders by @nihgwu in #1944
• feat(adapters/cloudflare): build static files with vite preview server by @dai-shi in #1943
• chore: update some dependencies by @dai-shi in #1949

New Contributors

• @Ariel-GonzAguer made their first contribution in #1926
• @yunho1017 made their first contribution in #1931
• @pavan-sh made their first contribution in #1946

Full Changelog: v1.0.0-alpha.3...v1.0.0-alpha.4

v1.0.0-alpha.3

This release includes various improvements and updates React in our templates.

What's Changed

• fix(router): unstable_routeInterceptor by @dai-shi in #1914
• refactor(vite-plugins): avoid estree types by @dai-shi in #1916
• fix(managed): exclude test and spec files from middleware auto-discovery by @struong in #1920
• breaking(minimal): rename renderHtml option by @dai-shi in #1924
• feat: support for csp by @dai-shi in #1922
• fix(router): restore router prefetch behavior by @dai-shi in #1915
• chore: update react by @dai-shi in #1930
• chore: update deps by @dai-shi in #1934

New Contributors

• @struong made their first contribution in #1920

Full Changelog: v1.0.0-alpha.2...v1.0.0-alpha.3

v1.0.0-alpha.2

Includes a bunch of small fixes.

What's Changed

• fix(router): typegen plugin without getConfig functions by @dai-shi in #1899
• fix(router): expose client internals by @dai-shi in #1898
• fix(internals): expose combined plugins by @dai-shi in #1900
• fix(adapter): Polish Cloudflare default config by @Master-Hash in #1892
• fix(router): typegen plugin without getConfig functions again by @dai-shi in #1902

New Contributors

• @deepso7 made their first contribution in #1889
• @Master-Hash made their first contribution in #1892

Full Changelog: v1.0.0-alpha.1...v1.0.0-alpha.2

v1.0.0-alpha.1

Excited to release Waku v1-alpha.1! This release improves support for Cloudflare Workers and introduces a breaking change to API route handling.

Migration Guide

Previously, API routes with file-based routing used ./src/pages/api/. In v1-alpha.1, this directory has been renamed to ./src/pages/_api/, and the _api/ segment is stripped from the URL path.

To preserve the api/ prefix in your URLs, move your previous ./src/pages/api/ directory to ./src/pages/_api/api/.

See #1885 for more information.

What's Changed

• feat(internals): expose resolveConfig etc. by @dai-shi in #1877
• refactor(adapter): pass handlers to adapters by @dai-shi in #1879
• breaking: Replace api/ directory with _api/ and strip prefix from routes by @Copilot in #1885
• feat: updated cloudflare adapter by @rmarscher in #1795

New Contributors

• @WuMingDao made their first contribution in #1874

Full Changelog: v1.0.0-alpha.0...v1.0.0-alpha.1

v1.0.0-alpha.0

Waku 1.0 (alpha)

Waku's public APIs are now marked as stable.

We're excited to announce the release of Waku 1.0-alpha!

Our public API surface area is now stable as we shift focus towards bug fixes and compatibility. Moving forward we'll write release notes with each version and provide migration guides if needed.

Waku shines for mostly-static sites with some dynamic routes (marketing sites, blogs, docs, light ecommerce). The simple per-route config makes it easy to go fully static or fully dynamic. Or even blend static and dynamic with layouts, slices, and pages each having their own rendering config.

Our updated home page now also includes config-based routing examples for those who prefer a programmatic approach instead of file-based routing.

We'd love for you to help us battle-test Waku! We invite you to try it on a side project over the holiday break. Let us know how it goes in our GitHub discussions or Discord server. Your feedback will help us work towards v1-beta and v1-rc.

Happy holidays! 🎄

---

Release notes

Breaking change

We've renamed the entry files from server-entry.ts(x) and client-entry.ts(x) to waku.server.ts(x) and waku.client.ts(x). This affects those who were using config-based routing or deployment adapters.