Waku
UnclaimedThe minimal React framework for building lightweight web applications with React 19 features.
Visit WebsiteFreeVisit Website
TL;DR - Waku
- Minimal React framework supporting React 19 features like server components and actions.
- Enables full-stack composability with flexible server-client boundary management.
- Ideal for marketing sites, headless commerce, and web apps, with smaller client bundle sizes.
Pricing: Free forever
Best for: Individuals & startups
Pros & Cons
Pros
- Lightweight and minimal framework
- Supports latest React 19 features
- Enables full-stack composability
- Potentially smaller client bundle sizes
- Simplifies full-stack development by integrating server and client logic
Cons
- Currently recommended for non-production projects
- May have a learning curve for modern React rendering patterns
- Not recommended for large enterprise applications
Preview
Key Features
Supports React 19 server componentsSupports React 19 actionsStatic prerendering (SSG)Server-side rendering (SSR)Flexible server-client boundary management with 'use client' directiveAsync server components for server-side logic and data fetchingClient components with traditional React features (state, effects, event handlers)Shared components usable in both server and client environments
Pricing
Free
Waku is completely free to use with no hidden costs.
About Waku
By Toolradar Team·
Waku is a minimal React framework designed to provide a lightweight and enjoyable developer experience, while fully supporting the latest React 19 features, including server components and actions. It enables full-stack composability by allowing developers to flexibly move server-client boundaries with a single line of code, simplifying the development of full-stack React applications compared to maintaining separate backend and frontend codebases.
This framework is particularly well-suited for marketing sites, headless commerce platforms, and general web applications. It emphasizes smaller client bundle sizes by leveraging server components. Waku supports both static prerendering (SSG) and server-side rendering (SSR) for layouts and pages, integrating seamlessly with server and client components. While it offers powerful patterns for modern React rendering, it's noted that larger enterprise applications might benefit from heavier frameworks.
Waku introduces a clear distinction between server components (which handle server-side logic, data fetching, and can access the file system without being included in the client bundle) and client components (which use traditional React features like state and interactivity and run in the browser). It also defines shared components that can be used in both environments. The framework is currently recommended for non-production projects, with an open invitation for contributors.
How we evaluate tools →Source: waku.gg
Reviews
No reviews yet. Be the first to review Waku!
Explore More
Waku FAQ
What are the recommended Node.js versions for running Waku projects?
Waku projects require Node.js version ^24.0.0, ^22.12.0, or ^20.19.0. Ensuring your environment meets these requirements will allow for proper development and deployment.
How does Waku handle server-client boundaries with the 'use client' directive?
The 'use client' directive establishes a server-client boundary when a client component is imported into a server component. All components imported below this boundary are then hydrated and executed in the browser, enabling traditional React features like state and event handlers.
Can client components import server components directly in Waku?
Client components cannot directly import server components. However, client components can accept server components as props, such as
children, which allows for patterns like adding global context providers.What rendering options does Waku provide for layouts and pages?
Waku offers both static prerendering (SSG) and server-side rendering (SSR) for layouts and pages. These options apply to all server and client components within the application.
How does Waku's approach to client components affect bundle size compared to traditional React frameworks?
Even with minimal optimization towards server components, Waku aims to produce smaller client bundle sizes. This is because traditional React frameworks typically treat all components as 100% client components, while Waku leverages server components to reduce the client-side footprint.
What types of applications is Waku best suited for, and are there any limitations for larger projects?
Waku is designed for marketing sites, headless commerce, and web apps, offering a lightweight and enjoyable developer experience. For large enterprise applications, a heavier framework might be more suitable.
Source: waku.gg