{"full_name":"infernojs/inferno","owner":"infernojs","name":"inferno","shard":"1","url":"https://github.com/infernojs/inferno","description":":fire: An extremely fast, React-like JavaScript library for building modern user interfaces","homepage":"https://infernojs.org","topics":["inferno","vdom","performance","react","javascript-library","inferno-js","jsx","inferno-component"],"tag_pages":["javascript-library","jsx","performance","react","vdom"],"language":"JavaScript","license":"MIT","avatar":"https://avatars.githubusercontent.com/u/14214240?v=4","created_at":"2015-02-01T22:07:38Z","pushed_at":"2026-11-15T06:57:55Z","metrics":{"stars":16459,"forks":642,"watchers":253,"issues":910,"prs":777,"releases":203,"issues_open":34,"issues_closed":876,"prs_open":1,"prs_closed":181,"prs_merged":595,"discussions":15},"growth":{"day":{"stars":0,"forks":0,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[16460,16461,16459,16459,16459,16459,16459],"forks":[642,642,642,642,642,642,642],"watchers":[null,253,253,253,253,253,253],"issues_open":[null,34,34,34,34,34,34],"prs_open":[null,1,1,1,2,2,1]},"boards":{},"same_owner":[],"issues":[{"number":1453,"title":"useState hook","comments":38,"created_at":"2019-02-27T21:06:26Z"},{"number":1496,"title":"Synchronous setState","comments":15,"created_at":"2019-11-09T15:04:24Z"},{"number":1204,"title":"Feature request: support promises in lifecycle components.","comments":10,"created_at":"2017-09-01T16:27:52Z"},{"number":1459,"title":"Inferno hydrate promise","comments":9,"created_at":"2019-03-18T19:46:28Z"},{"number":1443,"title":"Implement support for Inferno.memo ( React.memo )","comments":9,"created_at":"2019-02-08T19:35:19Z"},{"number":1073,"title":"Support react-optimize","comments":8,"created_at":"2017-05-12T05:31:26Z"},{"number":1266,"title":"will the next next version  coming with any mechanism of error processing","comments":7,"created_at":"2018-01-31T01:37:37Z"},{"number":377,"title":"Support Passive Event Listeners","comments":7,"created_at":"2016-09-21T15:34:29Z"}],"discussions":[{"number":1695,"title":"Correct return type for `render()` method","comments":1,"category":"General","created_at":"2026-03-13T13:48:31Z"},{"number":1688,"title":"possible to remove/add elements without rerender of entire app tree?","comments":1,"category":"Q&A","created_at":"2025-11-04T08:17:56Z"},{"number":1681,"title":"possible to `dangerouslySetInnerHTML` at Fragment?","comments":1,"category":"Q&A","created_at":"2025-07-19T18:15:52Z"},{"number":1679,"title":"edge-case, inferno needs care to render BODY vnode to the document","comments":1,"category":"General","created_at":"2025-06-17T19:01:16Z"},{"number":1659,"title":"Will inferno support signals?","comments":0,"category":"Q&A","created_at":"2023-12-03T18:13:26Z"},{"number":1655,"title":"Would be cool to see how Inferno syntax compares to other Javascript frameworks","comments":1,"category":"General","created_at":"2023-11-19T00:23:45Z"},{"number":1649,"title":"Revamp project","comments":2,"category":"Ideas","created_at":"2023-08-03T12:57:12Z"},{"number":1647,"title":"What is the right way to accept components as children only with a specific props shape?","comments":0,"category":"Q&A","created_at":"2023-06-27T11:06:17Z"}],"latest_release":{"name":"v10.0.0","tag":"v10.0.0","published_at":"2026-10-04T12:31:13Z","body":"# InfernoJS v10.0.0\r\n\r\nInferno 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.\r\n\r\nThis 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 bindings.\r\n\r\n## Upgrading\r\n\r\n1. Update every `inferno*` package to 10.\r\n2. Update your JSX plugin to version 10:\r\n\r\n   | Plugin                                                                      | Inferno 9 and older | Inferno 10 |\r\n   | --------------------------------------------------------------------------- | ------------------- | ---------- |\r\n   | [`babel-plugin-inferno`](https://github.com/infernojs/babel-plugin-inferno) | 7.x                 | 10.x       |\r\n   | [`ts-plugin-inferno`](https://github.com/infernojs/ts-plugin-inferno)       | 7.x                 | 10.x       |\r\n   | [`swc-plugin-inferno`](https://github.com/infernojs/swc-plugin-inferno)     | 3.x                 | 10.x       |\r\n\r\n   Version 10 of `babel-plugin-inferno` and `ts-plugin-inferno` requires Node.js 24 or newer to compile JSX. `ts-plugin-inferno` depends on TypeScript 6.\r\n\r\n3. Compile all your JSX again, including dependencies that ship precompiled JSX.\r\n4. If you write your own `componentWillMove` or `onComponentWillMove` hooks, add `import 'inferno-animation'`. See [Move animation hooks](#move-animation-hooks).\r\n5. Compile your own components to ES2015 or newer. A component class compiled to an ES5 function can no longer extend `Component`. See [Browser support](#browser-support).\r\n\r\nFrom version 10 on, the major version of each JSX plugin matches the major version of Inferno.\r\n\r\nEach change is described in detail in the [Migration guide](https://github.com/infernojs/inferno/blob/master/documentation/v10-migration.md).\r\n\r\n## Breaking changes\r\n\r\n- **JSX must be compiled by the v10 plugins.** `VNodeFlags` have new values, so JSX compiled by an older plugin renders elements such as `<svg>`, `<input>`, `<select>` and `<textarea>` wrong. This includes npm packages that ship JSX compiled for Inferno 9.\r\n- **`VNodeFlags` have new values.** Code compiled with `tsc` against `inferno-vnode-flags` 9 has the old numbers inlined and must be compiled again. Never write flag numbers by hand.\r\n- **`vNode.childFlags` has been removed.** The shape of the children is stored in bits of `vNode.flags`. Test them with `VNodeFlags.HasKeyedChildren` and the other `Has*Children` bits, or get the old `ChildFlags` value with the new `getChildFlags(vNode)` export.\r\n- **`vNode.isValidated` has been removed.** It is the development-only `VNodeFlags.Validated` bit now.\r\n- **`$ReCreate` and `VNodeFlags.ReCreate` have been removed.** Change the key of an element to re-create it. The v10 plugins report `$ReCreate` as a build error.\r\n- **Delegated event handlers are stored on the element.** `$EV` is now a bitmask, and each handler is in its own property of the element, such as `$onClick`. This only matters to tools that read Inferno's internal DOM properties.\r\n- **Move animation hooks have new semantics.** See [below](#move-animation-hooks).\r\n- **Modern bundles, and `Component` is a native class in all of them.** See [Browser support](#browser-support).\r\n\r\n```jsx\r\n// v9\r\n<div $ReCreate>{content}</div>\r\n\r\n// v10: change the key whenever the element must be re-created\r\n<div key={version}>{content}</div>\r\n```\r\n\r\n### Move animation hooks\r\n\r\nThe reconciler no longer runs move animations itself. `inferno-animation` installs a move engine when it is imported.\r\n\r\n- Custom `componentWillMove` and `onComponentWillMove` hooks are only called when the app has imported `inferno-animation`. The e","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}