alibaba-fusion/next

🦍 A configurable component library for web built on React.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 15 minutes ago
Added to GitGenius on September 14th, 2026
Created on June 21st, 2018
Open Issues & Pull Requests: 269 (+0)
GitHub issues: Enabled
Number of forks: 597
Total Stargazers: 4,680 (+0)
Total Subscribers: 73 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.7 days
Mean response time: 87.3 days
90th percentile: 94.2 days
Tracked items: 68

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 922 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

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

Top labels

  • Stale (59)
  • 💬 Discussion (25)
  • 🐞 Bug (22)
  • Insufficient information (17)
  • Next release (12)
  • Technical Upgrade (6)
  • improvement (4)
  • 💡 Feature Request (4)

Most active issues this week

Detailed Description

Next is a configurable component library for web built on React that serves as an enterprise-class UI solution for backend systems.

The tool addresses the friction between designers and front-end developers by enabling designers to customize component UI through the Fusion Design collaboration platform and release themed npm packages that developers can use directly. This approach eliminates the need for developers to implement UI changes themselves or undergo repeated review cycles with designers. Developers receive code fragments through IceWorks, while designers get design materials via Fusion Cool, a Sketch plugin. The system guarantees consistency between code and visual designs by centralizing customization through the platform rather than requiring manual synchronization.

Teams building enterprise backend systems where designer-developer collaboration is a bottleneck should consider this library. It works best when your organization uses Sketch for design and wants to maintain a unified design system across multiple projects. The tool is particularly valuable if you have dedicated design teams creating custom themes, as it eliminates the traditional workflow of designers handing off designs that developers must then implement and iterate on. The README positions this as the primary use case rather than suggesting it as a general-purpose component library for all React projects.

The project maintains active test coverage tracking and welcomes pull requests. Development activity shows consistent engagement with the codebase through automated testing infrastructure and ongoing maintenance of the component library.