Our take
Activeregular commits and releases- Activity
- 73
- Community
- 81
- Issues
- 32
- Pull requests
- 60
+6 stars in the last 30 days
- More contributors than 78% of the projects we track
- Slower to close issues than 99% of the projects we track
Inferno is an actively maintained, focused UI library with regular releases, but its long median issue-close time is a practical support consideration.
Good fit if
- You want a React-like JavaScript UI library and can use its own JSX compilation plugins and runtime.
- Your application benefits from client or server rendering and the project’s virtual-DOM optimizations.
- You value a permissive MIT-licensed project with ongoing commits and releases, and do not require React Native.
Look elsewhere if
- You need React Native support, which Inferno explicitly does not provide.
- You need quick issue resolution: measured issue handling shows a long median time to close.
- Your team depends on broad compatibility with React APIs without reviewing inferno-compat limitations.
All health signals
| Last commit | 2026-10-07 (7 days ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 8 (latest v10.0.0, 2026-10-04) |
| Contributors | 100+ (top contributor: 46% of commits) |
| Issues closed, last 90 days | 5 (typically closed in 1020 days) |
| Pull requests merged, last 90 days | 3 (typically merged in 0 days) |
| Project age | 11 years |
Checked on 2026-10-15 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
16,459Forks
642Change since Nov 17, 2026: 0 stars·0 forks
Overview
Inferno is a JavaScript library for building high-performance user interfaces in the browser and on the server. It offers a React-like component model and virtual DOM, aiming to reduce rendering and update costs for real-time data views and large DOM trees.
It is designed for teams that want familiar component-based development with runtime optimizations, including compile-time JSX optimizations. It supports client rendering and server-side rendering, but does not target React Native.
Key Features
- Component-based architecture with one-way data flow and React-like APIs.
- Virtual DOM rendering and diffing, with compile-time JSX optimizations through Inferno plugins for Babel, SWC, and TypeScript.
- Client rendering and server-side rendering through
inferno-server, with hydration support. - Class and functional components, with lifecycle events available for both.
- Controlled form elements, fragments, refs, portals, and a partial synthetic event system.
- Optional JSX, hyperscript, or
createElementapproaches for creating virtual nodes.
Use Cases
- Build a browser application with frequent updates or large rendered trees, where rendering performance is a priority.
- Develop a React-like interface with JSX and component lifecycles, while using Inferno's own runtime and compiler integrations.
- Render pages on a Node.js server and hydrate them in the browser with Inferno's server-rendering packages.
- Port or adapt parts of a React-oriented application using
inferno-compat, after checking its compatibility limitations.
What you need
Detected in the repository
- Node.js (from package.json)
- Automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the core package:
npm install --save inferno
For JSX, install the compiler plugin appropriate to your toolchain. See the README for setup, add-ons, and usage details.
Alternatives
- react: React offers a broader component ecosystem and React Native support, while Inferno focuses on a lightweight, high-performance virtual DOM for web interfaces.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| inferno | JavaScript | MIT | 16.5k | Active |
| react | JavaScript | MIT | 251k | Active |
Considerations
Inferno relies on compile-time plugins for JSX optimizations, and the README notes that JSX compiled with older plugin major versions does not work with Inferno 10. Plan to align plugin and Inferno versions when upgrading. The measured project data indicates frequent commits and releases, with at least 100 contributors and no dependence on one dominant contributor; however, issues have taken a long time to close. The project is browser- and server-focused, not a React Native solution.
Found this useful?
Share it with someone who would like inferno.