wakujs/waku

⛩️ The minimal React framework

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 3rd, 2023
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 213
Total Stargazers: 6,441 (+0)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.8 hours
Mean response time: 3.8 days
90th percentile: 2.3 days
Tracked items: 222

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 8% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 317 days
Stale 30+ days: 2
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (36)
  • bug (8)
  • good first issue (3)
  • enhancement (2)
  • documentation (1)
  • question (1)
  • upstream (1)

Detailed Description

Waku is a minimal React framework designed for building marketing sites, headless commerce, and full-stack web applications with a focus on lightweight architecture and developer experience.

The framework addresses the complexity of modern React development by embracing server components and server actions as first-class patterns. It solves the problem of bundle size and full-stack code organization by allowing developers to flexibly move server-client boundaries within a single React codebase. The approach centers on composing with ecosystem libraries rather than the framework owning those concerns, keeping the framework surface minimal while supporting React 19 features including server components, client components, and shared components that work across both boundaries.

Waku suits developers who want a lightweight foundation and prefer explicit control over server-client separation through the `'use client'` directive. It works well for projects of any size where the architecture matters more than project scope, and where teams want to avoid maintaining separate backend and frontend codebases. The framework is built for those comfortable with modern React rendering patterns and willing to learn server component semantics in exchange for smaller client bundles and powerful full-stack composability. It differs from heavier frameworks by keeping its own surface minimal and delegating concerns like routing and state management to the ecosystem rather than providing opinionated built-in solutions.

The project maintains active development with regular updates to support the latest React features. Development is responsive to ecosystem changes and React specification evolution. The maintainers provide comprehensive learning resources including guided quick-start documentation and step-by-step tutorials on the project website.