InfernoJS Babel Plugin

Plugin for babel 6+ to enable JSX for Inferno

This plugin transforms JSX code in your projects to Inferno compatible virtual DOM. It is recommended to use this plugin for compiling JSX for inferno. It is different to other JSX plugins, because it outputs highly optimized inferno specific createVNode calls. This plugin also checks children shape during compilation stage to reduce overhead from runtime application.

How to install

1npm i --save-dev babel-plugin-inferno

How to use

Add the plugin to your package.json and update the plugin section in your .babelrc file. Or if your Babel settings are located inside the package.json - update the plugin section there.

It's important that you also include the babel-plugin-syntax-jsxplugin.

Example on a .babelrc file that will work with Inferno:

Make sure inferno plugin is added before babel module transformers

1{   
2    "presets": [ "es2015" ],
3    "plugins": [["babel-plugin-inferno", {"imports": true}]]
4}

Examples

1
2// Render a simple div
3Inferno.render(<div></div>, container);
4
5// Render a div with text
6Inferno.render(<div>Hello world</div>, container);
7
8// Render a div with a boolean attribute
9Inferno.render(<div autoFocus='true' />, container);
10

Fragments

All of the following syntaxes are reserved for createFragment call

1<>
2    <div>Foo</div>
3    <div>Bar</div>
4</>
5
6
7<Fragment>
8    <div>Foo</div>
9    <div>Bar</div>
10</Fragment>
11
12<Inferno.Fragment>
13    <div>Foo</div>
14    <div>Bar</div>
15</Inferno.Fragment>
16

React.Fragment is also compiled to inferno createFragment call to ease project migration to Inferno https://github.com/infernojs/babel-plugin-inferno/issues/56.

Special flags

This plugin provides few special compile time flags that can be used to optimize an inferno application.

1// ChildFlags:
2<div $HasTextChildren /> - Children is rendered as pure text
3<div $HasVNodeChildren /> - Children is another vNode (Element or Component)
4<div $HasNonKeyedChildren /> - Children is always array without keys
5<div $HasKeyedChildren /> - Children is array of vNodes having unique keys
6<div $ChildFlag={expression} /> - This attribute is used for defining children shpae runtime. See inferno-vnode-flags (ChildFlags) for possibe values
7
8// Functional flags
9<div $ReCreate /> - This flag tells inferno to always remove and add the node. It can be used to replace key={Math.random()}

Flag called noNormalize has been removed in v4, and is replaced by $HasVNodeChildren

Options

Change in v4:

Imports (boolean)

babel-plugin-inferno will automatically import the required methods from inferno library. There is no need to import inferno in every single JSX file. Only import the inferno specific code required by the application.

example:

1import {render} from 'inferno'; // Just import what you need, (render in this case)
2
3// The plugin will automatically import, createVNode
4render(<div>1</div>, document.getElementById('root'));

You need to have support for ES6 modules for this to work. If you are using legacy build system or outdated version of webpack, you can revert this change by using imports: false

1{
2    "presets": [ "es2015" ],
3    "plugins": [["inferno", {
4        "imports": false
5    }]]
6}

Pragma

Each method that is used from inferno can be replaced by custom name.

pragma (string) defaults to createVNode.

pragmaCreateComponentVNode (string) defaults to createComponentVNode.

pragmaNormalizeProps (string) defaults to normalizeProps.

pragmaTextVNode (string) defaults to createTextVNode.

pragmaFragmentVNode (string) defaults to createFragment.

1{
2    "presets": [ "es2015" ],
3    "plugins": [["inferno", {
4        "imports": true,
5        "pragma": "",
6        "pragmaCreateComponentVNode": "",
7        "pragmaNormalizeProps": "",
8        "pragmaTextVNode": ""
9    }]]
10}

Troubleshoot

You can verify babel-plugin-inferno is used by looking at the compiled output. This plugin does not generate calls to createElement or h, but instead it uses low level InfernoJS API createVNode, createComponentVNode, createFragment etc. If you see your JSX being transpiled into createElement calls its good indication that your babel configuration is not correct.