tencent/wujie

极致的微前端框架

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 13th, 2026
Created on June 29th, 2022
Open Issues & Pull Requests: 450 (+0)
GitHub issues: Enabled
Number of forks: 680
Total Stargazers: 5,045 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.6 days
Mean response time: 105.9 days
90th percentile: 378.2 days
Tracked items: 244

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 35% of issues opened in the past year have been closed. Three people close 72% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 171
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 704 days
Stale 30+ days: 164
Stale 90+ days: 161

Recent activity

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

Top labels

  • bug (3)
  • to do list (3)
  • enhancement (1)
  • good question (1)
  • lib bug (1)

Most active issues this week

Detailed Description

Wujie is a micro frontend framework that combines Web Components and iframe sandboxing to isolate child applications.

The framework addresses core pain points in existing micro frontend solutions: adaptation costs, style isolation, runtime performance, initial page load times, inter-application communication, child application persistence, and multi-application activation. It achieves this by leveraging Web Components for strict CSS style isolation and iframes for native JavaScript runtime isolation, giving each child application its own independent window, document, history, and location objects. This approach provides native-level isolation without requiring custom sandbox construction.

Teams should choose this framework if they need low adaptation costs for both host and child applications, fast child application startup and execution, and strong isolation guarantees. It supports child application nesting, multiple simultaneous active applications, application state persistence, decentralized communication patterns, lifecycle hooks, a plugin system, and Vite framework compatibility. The framework suits projects where existing micro frontend solutions have created problems around style leakage, performance bottlenecks, or communication complexity.

The project maintains active development with regular updates to the codebase and documentation. The team responds to issues and pull requests, indicating ongoing engagement with the user community. Development appears focused on stability and feature completeness rather than rapid experimental changes, with attention to supporting multiple framework integrations and addressing real-world deployment scenarios.