infernojs /inferno
:fire: An extremely fast, React-like JavaScript library for building modern user interfaces
★ 16,459⑂ 642👁 253⑃ 777● 910▤ 203
+0
Daily
16,459
stars
642
forks
253
watchers
777
prs
910
issues
203
releases
README
Inferno is an insanely fast, React-like library for building high-performance user interfaces on both the client and server. Description The main objective of the InfernoJS project is to provide the fastest possible runtime performance for web applications. Inferno excels at rendering real time data views or large DOM trees. The performance is achieved through multiple optimizations, for example: - Inferno's own JSX compilers creates monomorphic newVNode calls, instead of createElement calls. Optimizing runtime performance of the application. - SWC plugin inferno is a plugin for SWC. It can compile TSX and JSX - Babel plugin inferno is a plugin for BabelJs. It can compile JSX. - TS plugin inferno is a plugin for TSC. It can compile TSX. - Inferno 10 needs version 10 of these plugins, and JSX compiled by older versions does not work with it. From version 10 on, the major version of each plugin matches the major version of Inferno. See the v10 migration guide. - Inferno's diff process uses bitwise flags to memoize the shape of objects - Child nodes are normalized only when needed - Special JSX flags can be used during compile time to optimize runtime performance at application level - Many micro optimizations Features - Component driven + one-way data flow architecture - React-like API, concepts and component lifecycle events - Partial synthetic event system, normalizing events for better cross browser support - Inferno's linkEvent feature removes the need to use arrow functions or binding event callbacks - Isomorphic rendering on both client and server with inferno-server - Unlike React and Preact, Inferno has lifecycle events on functional components - Unlike Preact and other React-like libraries, Inferno has controlled components for input/select/textarea elements - Components can be rendered outside their current html hierarchy using createPortal - API - Support for older browsers without any polyfills - defaultHooks for Functional components, this way re-defining lifecycle events per usage can be avoided - Inferno supports setting styles using string or using object literal syntax . For camelCase syntax support see inferno-compat. - Fragments (v6) - createRef and forwardRef APIs (v6) - componentDidAppear, componentWillDisappear and componentWillMove (v8) - class and function component callbacks to ease animation work, see inferno-animation package Runtime requirements Inferno v9 requires following features to be present in the executing runtime: - Promise - String.prototype.includes() - String.prototype.startsWith() - Array.prototype.includes() - Object.spread() - for ... of Browser support Since version 4 we have started running our test suite without any polyfills. Inferno is now part of Saucelabs open source program and we use their service for executing the tests. InfernoJS is actively tested with browsers listed below, however it may run well on older browsers as well. This is due to limited support of browser vers
Top issues
#1453useState hook38 comments · 2019-02-27#1496Synchronous setState15 comments · 2019-11-09#1204Feature request: support promises in lifecycle components.10 comments · 2017-09-01#1459Inferno hydrate promise9 comments · 2019-03-18#1443Implement support for Inferno.memo ( React.memo )9 comments · 2019-02-08#1073Support react-optimize8 comments · 2017-05-12#1266will the next next version coming with any mechanism of error processing7 comments · 2018-01-31#377Support Passive Event Listeners7 comments · 2016-09-21
Discussions
#1695Correct return type for `render()` method1 comments · 2026-03-13#1688possible to remove/add elements without rerender of entire app tree?1 comments · 2025-11-04#1681possible to `dangerouslySetInnerHTML` at Fragment?1 comments · 2025-07-19#1679edge-case, inferno needs care to render BODY vnode to the document1 comments · 2025-06-17#1659Will inferno support signals?0 comments · 2023-12-03#1655Would be cool to see how Inferno syntax compares to other Javascript frameworks1 comments · 2023-11-19#1649Revamp project2 comments · 2023-08-03#1647What is the right way to accept components as children only with a specific props shape?0 comments · 2023-06-27
Latest release
v10.0.0 v10.0.0 2026-10-04InfernoJS v10.0.0 Inferno 10 moves work from the runtime to the compiler. The JSX plugins know the shape of an element's children when they compile it, so they now write it into the vNode flags. Inferno no longer computes it for every vNode at runtime. A vNode has one field less, delegated event handlers take less memory, and many allocations are gone from rendering, normalization and keyed diffing. This release also rewrites inferno-animation, adds custom navigation confirmation to inferno-router, and fixes many bugs in core, hydration, server rendering, the router, compat and the MobX