"Waku, a minimal React framework has released version 1.0 alpha, marking its public API surface area as stable as the project shifts focus towards bug fixes and compatibility improvements. Waku 1.0 alpha represents a significant milestone for the lightweight framework, which has been in development for nearly three years. The release stabilises the framework's public APIs and signals a transition from feature development to refinement and stability."
"One of the key strengths highlighted in this release is Waku's sweet spot for mostly-static sites with some dynamic routes, including marketing sites, blogs, documentation sites, and light ecommerce applications. The framework's simple per-route configuration makes it straightforward to choose between fully static or fully dynamic rendering, or even blend the two approaches with layouts, slices, and pages each having their own rendering configuration."
"The 1.0 alpha release introduces a breaking change vs earlier releases, that affects users implementing config-based routing or deployment adapters. Entry files have been renamed from server-entry.ts and client-entry.ts to waku.server.ts and waku.client.ts respectively. Developers upgrading from earlier versions will need to rename these files accordingly. There is no migration guide for the release, but there is an earlier community-created migration guide provides detailed upgrade instructions for users moving from version 0.25 to 0.27."
Waku 1.0 alpha marks the framework's public API as stable and shifts development toward bug fixes, compatibility, and refinement. The framework has been in development nearly three years and the team will provide release notes and migration guides when needed as they progress toward 1.0 beta and release candidate stages. Waku fits mostly-static sites with some dynamic routes, such as marketing sites, blogs, documentation, and light ecommerce, and offers simple per-route configuration to select static, dynamic, or mixed rendering for layouts, slices, and pages. The release renames entry files and introduces a breaking change for config-based routing and deployment adapters, requiring file renames.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]