:fire: An extremely fast, React-like JavaScript library for building modern user interfaces

Overview

Inferno

Build Status Coverage Status MIT NPM npm downloads Slack Status gzip size Backers on Open Collective Sponsors on Open Collective lerna

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 plugin creates monomorphic createVNode calls, instead of createElement
  • 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 <div style="background-color: red"></div> or using object literal syntax <div style={{"background-color": "red"}}></div>. For camelCase syntax support see inferno-compat.
  • Fragments (v6)
  • createRef and forwardRef APIs (v6)

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 natively supports the browsers listed below.

Build Status

Migration guides

Benchmarks

Live examples at https://infernojs.github.io/inferno

Code Example

Let's start with some code. As you can see, Inferno intentionally keeps the same design ideas as React regarding components: one-way data flow and separation of concerns.

In these examples, JSX is used via the Inferno JSX Babel Plugin to provide a simple way to express Inferno virtual DOM. You do not need to use JSX, it's completely optional, you can use hyperscript or createElement (like React does). Keep in mind that compile time optimizations are available only for JSX.

import { render } from 'inferno';

const message = "Hello world";

render(
  <MyComponent message={ message } />,
  document.getElementById("app")
);

Furthermore, Inferno also uses ES6 components like React:

import { render, Component } from 'inferno';

class MyComponent extends Component {
  constructor(props) {
    super(props);
    this.state = {
      counter: 0
    };
  }
  render() {
    return (
      <div>
        <h1>Header!</h1>
        <span>Counter is at: { this.state.counter }</span>
      </div>
    );
  }
}

render(
  <MyComponent />,
  document.getElementById("app")
);

Because performance is an important aspect of this library, we want to show you how to optimize your application even further. In the example below we optimize diffing process by using JSX $HasVNodeChildren to predefine children shape compile time. Then we create text vNode using createTextVNode. All child flags are documented here.

import { createTextVNode, render, Component } from 'inferno';

class MyComponent extends Component {
  constructor(props) {
    super(props);
    this.state = {
      counter: 0
    };
  }
  render() {
    return (
      <div>
        <h1>Header!</h1>
        <span $HasVNodeChildren>{createTextVNode('Counter is at: ' + this.state.counter)}</span>
      </div>
    );
  }
}

render(
  <MyComponent />,
  document.getElementById("app")
);

Tear down

To tear down inferno application you need to render null on root element. Rendering null will trigger unmount lifecycle hooks for whole vDOM tree and remove global event listeners. It is important to unmount unused vNode trees to free browser memory.

import { createTextVNode, render, Component } from 'inferno';

const rootElement = document.getElementById("app");

// Start the application
render(
  <ExampleComponent/>,
  rootElement
);

// Tear down
render(
  null,
  rootElement
);

More Examples

If you have built something using Inferno you can add them here:

Getting Started

The easiest way to get started with Inferno is by using Create Inferno App.

Alternatively, you can try any of the following:

Core package:

npm install --save inferno

Addons:

# server-side rendering
npm install --save inferno-server
# routing
npm install --save inferno-router

Pre-bundled files for browser consumption can be found on our cdnjs:

Or on jsDelivr:

https://cdn.jsdelivr.net/npm/[email protected]/dist/inferno.min.js

Or on unpkg.com:

https://unpkg.com/[email protected]/dist/inferno.min.js

Creating Virtual DOM

JSX:

npm install --save-dev babel-plugin-inferno

Hyperscript:

npm install --save inferno-hyperscript

createElement:

npm install --save inferno-create-element

Compatibility with existing React apps

npm install --save-dev inferno-compat

Note: Make sure you read more about inferno-compat before using it.

Third-party state libraries

Inferno now has bindings available for some of the major state management libraries out there:

JSX

Inferno has its own JSX Babel plugin.

Differences from React

  • Inferno doesn't have a fully synthetic event system like React does. Inferno has a partially synthetic event system, instead opting to only delegate certain events (such as onClick).
  • Inferno doesn't support React Native. Inferno was only designed for the browser/server with the DOM in mind.
  • Inferno doesn't support legacy string refs, use createRef or callback ref API
  • Inferno provides lifecycle events on functional components. This is a major win for people who prefer lightweight components rather than ES2015 classes.
  • Inferno is able to use the React Dev Tools extensions for Chrome/Firefox/etc to provide the same level of debugging experience to the Inferno user via inferno-devtools.

Differences from Preact

  • Inferno has a partial synthetic event system, resulting in better performance via delegation of certain events.
  • Inferno is much faster than Preact in rendering, updating and removing elements from the DOM. Inferno diffs against virtual DOM, rather than the real DOM (except when loading from server-side rendered content), which means it can make drastic improvements. Unfortunately, diffing against the real DOM has a 30-40% overhead cost in operations.
  • Inferno fully supports controlled components for input/select/textarea elements. This prevents lots of edgecases where the virtual DOM is not the source of truth (it should always be). Preact pushes the source of truth to the DOM itself.
  • Inferno provides lifecycle events on functional components. This is a major win for people who prefer lightweight components rather than ES2015 classes.

Event System

Like React, Inferno also uses a light-weight synthetic event system in certain places (although both event systems differ massively). Inferno's event system provides highly efficient delegation and an event helper called linkEvent.

One major difference between Inferno and React is that Inferno does not rename events or change how they work by default. Inferno only specifies that events should be camel cased, rather than lower case. Lower case events will bypass Inferno's event system in favour of using the native event system supplied by the browser. For example, when detecting changes on an <input> element, in React you'd use onChange, with Inferno you'd use onInput instead (the native DOM event is oninput).

Available synthetic events are:

  • onClick
  • onDblClick
  • onFocusIn
  • onFocusOut
  • onKeyDown
  • onKeyPress
  • onKeyUp
  • onMouseDown
  • onMouseMove
  • onMouseUp
  • onTouchEnd
  • onTouchMove
  • onTouchStart

linkEvent (package: inferno)

linkEvent() is a helper function that allows attachment of props/state/context or other data to events without needing to bind() them or use arrow functions/closures. This is extremely useful when dealing with events in functional components. Below is an example:

import { linkEvent } from 'inferno';

function handleClick(props, event) {
  props.validateValue(event.target.value);
}

function MyComponent(props) {
  return <div><input type="text" onClick={ linkEvent(props, handleClick) } /><div>;
}

This is an example of using it with ES2015 classes:

import { linkEvent, Component } from 'inferno';

function handleClick(instance, event) {
  instance.setState({ data: event.target.value });
}

class MyComponent extends Component {
  render () {
    return <div><input type="text" onClick={ linkEvent(this, handleClick) } /><div>;
  }
}

linkEvent() offers better performance than binding an event in a class constructor and using arrow functions, so use it where possible.

Controlled Components

In HTML, form elements such as <input>, <textarea>, and <select> typically maintain their own state and update it based on user input. In Inferno, mutable state is typically kept in the state property of components, and only updated with setState().

We can combine the two by making the Inferno state be the "single source of truth". Then the Inferno component that renders a form also controls what happens in that form on subsequent user input. An input form element whose value is controlled by Inferno in this way is called a "controlled component".

Inferno Top-Level API

render (package: inferno)

import { render } from 'inferno';

render(<div />, document.getElementById("app"));

Render a virtual node into the DOM in the supplied container given the supplied virtual DOM. If the virtual node was previously rendered into the container, this will perform an update on it and only mutate the DOM as necessary, to reflect the latest Inferno virtual node.

Warning: If the container element is not empty before rendering, the content of the container will be overwritten on the initial render.

createRenderer (package: inferno)

createRenderer creates an alternative render function with a signature matching that of the first argument passed to a reduce/scan function. This allows for easier integration with reactive programming libraries, like RxJS and Most.

import { createRenderer } from 'inferno';
import { scan, map } from 'most';

const renderer = createRenderer();


// NOTE: vNodes$ represents a stream of virtual DOM node updates
scan(renderer, document.getElementById("app"), vNodes$);

See inferno-most-fp-demo for an example of how to build an app architecture around this.

createElement (package: inferno-create-element)

Creates an Inferno VNode using a similar API to that found with React's createElement()

import { Component, render } from 'inferno';
import { createElement } from 'inferno-create-element';

class BasicComponent extends Component {
  render() {
    return createElement('div', {
        className: 'basic'
      },
      createElement('span', {
        className: this.props.name
      }, 'The title is ', this.props.title)
    )
  }
}

render(
  createElement(BasicComponent, { title: 'abc' }),
  document.getElementById("app")
);

Component (package: inferno)

Class component:

import { Component } from 'inferno';

class MyComponent extends Component {
  render() {
    ...
  }
}

This is the base class for Inferno Components when they're defined using ES6 classes.

Functional component:

const MyComponent = ({ name, age }) => (
  <span>My name is: { name } and my age is: {age}</span>
);

Another way of using defaultHooks.

export function Static() {
    return <div>1</div>;
}

Static.defaultHooks = {
    onComponentShouldUpdate() {
        return false;
    }
};

Default props


Functional components are first-class functions where their first argument is the props passed through from their parent.

createVNode (package: inferno)

import { createVNode } from 'inferno';

createVNode(
  flags,
  type,
  [className],
  [...children],
  [childFlags],
  [props],
  [key],
  [ref]
)

createVNode is used to create html element's virtual node object. Typically createElement() (package: inferno-create-element), h() (package: inferno-hyperscript) or JSX are used to create VNodes for Inferno, but under the hood they all use createVNode(). Below is an example of createVNode usage:

import { VNodeFlags, ChildFlags } from 'inferno-vnode-flags';
import { createVNode, createTextVNode, render } from 'inferno';

const vNode = createVNode(VNodeFlags.HtmlElement, 'div', 'example', createTextVNode('Hello world!'), ChildFlags.HasVNodeChildren);

// <div class="example">Hello world!</div>

render(vNode, container);

createVNode arguments explained:

flags: (number) is a value from VNodeFlags, this is a numerical value that tells Inferno what the VNode describes on the page.

type: (string) is tagName for element for example 'div'

className: (string) is the class attribute ( it is separated from props because it is the most commonly used property )

children: (vNode[]|vNode) is one or array of vNodes to be added as children for this vNode

childFlags: (number) is a value from ChildFlags, this tells inferno shape of the children so normalization process can be skipped.

props: (Object) is object containing all other properties. fe: {onClick: method, 'data-attribute': 'Hello Community!}

key: (string|number) unique key within this vNodes siblings to identify it during keyed algorithm.

ref: (function) callback which is called when DOM node is added/removed from DOM.

createComponentVNode (package: 'inferno')

import { createComponentVNode } from 'inferno';

createComponentVNode(
  flags,
  type,
  [props],
  [key],
  [ref]
)

createComponentVNode is used for creating vNode for Class/Functional Component.

Example:

import { VNodeFlags, ChildFlags } from 'inferno-vnode-flags';
import { createVNode, createTextVNode, createComponentVNode, render } from 'inferno';

function MyComponent(props, context) {
  return createVNode(VNodeFlags.HtmlElement, 'div', 'example', createTextVNode(props.greeting), ChildFlags.HasVNodeChildren);
}

const vNode = createComponentVNode(VNodeFlags.ComponentFunction, MyComponent, {
  greeting: 'Hello Community!'
}, null, {
  onComponentDidMount() {
    console.log("example of did mount hook!")
  }
})

// <div class="example">Hello Community!</div>

render(vNode, container);

createComponentVNode arguments explained:

flags: (number) is a value from VNodeFlags, this is a numerical value that tells Inferno what the VNode describes on the page.

type: (Function/Class) is the class or function prototype for Component

props: (Object) properties passed to Component, can be anything

key: (string|number) unique key within this vNodes siblings to identify it during keyed algorithm.

ref: (Function|Object) this property is object for Functional Components defining all its lifecycle methods. For class Components this is function callback for ref.

createTextVNode (package: 'inferno')

createTextVNode is used for creating vNode for text nodes.

createTextVNode arguments explained: text: (string) is a value for text node to be created. key: (string|number) unique key within this vNodes siblings to identify it during keyed algorithm.

import { createTextVNode } from 'inferno';

createTextVNode(
  text,
  key
)

cloneVNode (package: inferno-clone-vnode)

This package has same API as React.cloneElement

import { cloneVNode } from 'inferno-clone-vnode';

cloneVNode(
  vNode,
  [props],
  [...children]
)

Clone and return a new Inferno VNode using a VNode as the starting point. The resulting VNode will have the original VNode's props with the new props merged in shallowly. New children will replace existing children. key and ref from the original VNode will be preserved.

cloneVNode() is almost equivalent to:

<VNode.type {...VNode.props} {...props}>{children}</VNode.type>

An example of using cloneVNode:

import { createVNode, render } from 'inferno';
import { cloneVNode } from 'inferno-clone-vnode';
import { VNodeFlags } from 'inferno-vnode-flags';

const vNode = createVNode(VNodeFlags.HtmlElement, 'div', 'example', 'Hello world!');
const newVNode = cloneVNode(vNode, { id: 'new' }); // we are adding an id prop to the VNode

render(newVNode, container);

If you're using JSX:

import { render } from 'inferno';
import { cloneVNode } from 'inferno-clone-vnode';

const vNode = <div className="example">Hello world</div>;
const newVNode = cloneVNode(vNode, { id: 'new' }); // we are adding an id prop to the VNode

render(newVNode, container);

createPortal (package: 'inferno')

HTML:

<div id="root"></div>
<div id="outside"></div>

Javascript:

const { render, Component, version, createPortal } from 'inferno';

function Outsider(props) {
	return <div>{`Hello ${props.name}!`}</div>;
}

const outsideDiv = document.getElementById('outside');
const rootDiv = document.getElementById('root');

function App() {
	return (
  	    <div>
    	    Main view
            ...
            {createPortal(<Outsider name="Inferno" />, outsideDiv)}
        </div>
    );
}


// render an instance of Clock into <body>:
render(<App />, rootDiv);

Results into:

<div id="root">
    <div>Main view ...</div>
</div>
<div id="outside">
    <div>Hello Inferno!</div>
</div>

Cool huh? Updates (props/context) will flow into "Outsider" component from the App component the same way as any other Component. For inspiration on how to use it click here!

createRef (package: inferno)

createRef API provides shorter syntax than callback ref when timing of element is not needed.

import { Component, render, createRef } from 'inferno';

class Foobar extends Component {
  constructor(props) {
    super(props);

    // Store reference somewhere
    this.element = createRef(); // Returns object {current: null}
  }

  render() {
    return (
      <div>
        <span id="span" ref={this.element}>
          Ok
        </span>
      </div>
    );
  }
}

render(<Foobar />, container);

createFragment (package: inferno)

createFragment is the native way to createFragment vNode. createFragment(children: any, childFlags: ChildFlags, key?: string | number | null)

createFragment arguments explained:

children: (Array) Content of fragment vNode, typically array of VNodes

childFlags: (number) is a value from ChildFlags, this tells inferno shape of the children so normalization process can be skipped.

key: (string|number) unique key within this vNodes siblings to identify it during keyed algorithm.

Alternative ways to create fragment vNode are:

  • Using JSX <> ... </>, <Fragment> .... </Fragment> or <Inferno.Fragment> ... </Inferno.Fragment>
  • Using createElement API createElement(Inferno.Fragment, {key: 'test'}, ...children)
  • Using hyperscript API h(Inferno.Fragment, {key: 'test'}, children)

In the below example both fragments are identical except they have different key

import { Fragment, render, createFragment } from 'inferno';
import { ChildFlags } from 'inferno-vnode-flags';

function Foobar() {
    return (
      <div $HasKeyedChildren>
        {createFragment(
            [<div>Ok</div>, <span>1</span>],
            ChildFlags.HasNonKeyedChildren,
            'key1'
        )}
        <Fragment key="key2">
          <div>Ok</div>
          <span>1</span>
        </Fragment>
      </div>
    );
}

render(<Foobar />, container);

forwardRef (package: inferno)

forwardRef is a new mechanism to "forward" ref inside a functional Component. It can be useful if you have simple functional Components and you want to create reference to a specific element inside it.

import { forwardRef, Component, render } from 'inferno';

const FancyButton = forwardRef((props, ref) => (
  <button ref={ref} className="FancyButton">
    {props.children}
  </button>
));

class Hello extends Component {
  render() {
    return (
      <FancyButton
        ref={btn => {
          if (btn) {
            // btn variable is the button rendered from FancyButton
          }
        }}
      >
        Click me!
      </FancyButton>
    );
  }
}

render(<Hello />, container);

hydrate (package: inferno-hydrate)

import { hydrate } from 'inferno-hydrate';

hydrate(<div />, document.getElementById("app"));

Same as render(), but is used to hydrate a container whose HTML contents were rendered by inferno-server. Inferno will attempt to attach event listeners to the existing markup.

options.componentComparator ( package inferno) DEV only

This option can be used during development to create custom component comparator method. This option will be called on every Component update. It gets two parameters: lastVNode and nextVNode. When it returns true lastVNode will be replaced with nextVNode. If anything else than true is returned it falls to normal behavior.

import {options} from 'inferno';

options.componentComparator = function (lastVNode, nextVNode) {
    /* custom logic */
    return true; // Replaces lastVNode with nextVNode
}

findDOMNode (package: inferno-extras)

This feature has been moved from inferno to inferno-compat in v6. No options are needed anymore.

Note: we recommend using a ref callback on a component to find its instance, rather than using findDOMNode(). findDOMNode() cannot be used on functional components.

If a component has been mounted into the DOM, this returns the corresponding native browser DOM element. This method is useful for reading values out of the DOM, such as form field values and performing DOM measurements. In most cases, you can attach a ref to the DOM node and avoid using findDOMNode() at all. When render returns null or false, findDOMNode() returns null. If Component has rendered fragment it returns the first element.

Inferno Flags (package: inferno-vnode-flags)

VNodeFlags:

  • VNodeFlags.HtmlElement
  • VNodeFlags.ComponentUnknown
  • VNodeFlags.ComponentClass
  • VNodeFlags.ComponentFunction
  • VNodeFlags.Text
  • VNodeFlags.SvgElement
  • VNodeFlags.InputElement
  • VNodeFlags.TextareaElement
  • VNodeFlags.SelectElement
  • VNodeFlags.Void
  • VNodeFlags.Portal
  • VNodeFlags.ReCreate (JSX $ReCreate) always re-creates the vNode
  • VNodeFlags.ContentEditable
  • VNodeFlags.Fragment
  • VNodeFlags.InUse
  • VnodeFlags.ForwardRef
  • VNodeFlags.Normalized

VNodeFlags Masks:

  • VNodeFlags.ForwardRefComponent Functional component wrapped in forward ref
  • VNodeFlags.FormElement - Is form element
  • VNodeFlags.Element - Is vNode element
  • VNodeFlags.Component - Is vNode Component
  • VNodeFlags.DOMRef - Bit set when vNode holds DOM reference
  • VNodeFlags.InUseOrNormalized - VNode is used somewhere else or came from normalization process
  • VNodeFlags.ClearInUseNormalized - Opposite mask of InUse or Normalized

ChildFlags

  • ChildFlags.UnknownChildren needs Normalization
  • ChildFlags.HasInvalidChildren is invalid (null, undefined, false, true)
  • ChildFlags.HasVNodeChildren (JSX $HasVNodeChildren) is single vNode (Element/Component)
  • ChildFlags.HasNonKeyedChildren (JSX $HasNonKeyedChildren) is Array of vNodes non keyed (no nesting, no holes)
  • ChildFlags.HasKeyedChildren (JSX $HasKeyedChildren) is Array of vNodes keyed (no nesting, no holes)
  • ChildFlags.HasTextChildren (JSX $HasTextChildren) vNode contains only text

ChildFlags Masks

  • ChildFlags.MultipleChildren Is Array

renderToString (package: inferno-server)

import { renderToString } from 'inferno-server';

const string = renderToString(<div />);

Render a virtual node into an HTML string, given the supplied virtual DOM.

Functional component lifecycle events

Name Triggered when Arguments to callback
onComponentWillMount a functional component is about to mount
onComponentDidMount a functional component has mounted successfully domNode
onComponentShouldUpdate a functional component has been triggered to update lastProps, nextProps
onComponentWillUpdate a functional component is about to perform an update lastProps, nextProps
onComponentDidUpdate a functional component has performed an update lastProps, nextProps
onComponentWillUnmount a functional component is about to be unmounted domNode

Class component lifecycle events

All these Component lifecycle methods ( including render and setState - callback) are called with Component instance context. You don't need to "bind" these methods.

Name Triggered when Arguments to callback
componentDidMount component has been mounted successfully
componentWillMount component is about to mount
componentWillReceiveProps  before render when component updates nextProps, context
shouldComponentUpdate  component has been triggered to update nextProps, nextState
componentWillUpdate component is about to perform an update nextProps, nextState, context
componentDidUpdate component has performed an update lastProps, lastState, snapshot
componentWillUnmount component is about to be unmounted
getChildContext before render method, return value object is combined to sub tree context
getSnapshotBeforeUpdate before component updates, return value is sent to componentDidUpdate as 3rd parameter lastProps, lastState
static getDerivedStateFromProps before render method nextProps, state

Using functional lifecycle events

Functional lifecycle events must be explicitly assigned via props onto a functional component like shown below:

import { render } from 'inferno';

function mounted(domNode) {
  // [domNode] will be available for DOM nodes and components (if the component has mounted to the DOM)
}

function FunctionalComponent({ props }) {
  return <div>Hello world</div>;
}

render(
  <FunctionalComponent onComponentDidMount={ mounted } />,
  document.getElementById("app")
);

Please note: class components (ES2015 classes) from inferno do not support the same lifecycle events (they have their own lifecycle events that work as methods on the class itself).

Development vs Production modes

By default, Inferno will run in development mode. Development mode provides extra checks and better error messages at the cost of slower performance and larger code to parse. When using Inferno in a production environment, it is highly recommended that you turn off development mode.

Running Inferno on Node JS

Ensure the environment variable process.env.NODE_ENV is set to production.

Building Inferno for use in a browser

When running Inferno on the browser using Webpack or Rollup, a replacement will need to occur during your build.

Webpack

Use the following configuration in your Webpack build for production build:

  ...
  plugins: [
    new webpack.DefinePlugin({
      'process.env': {
        'NODE_ENV': JSON.stringify('production')
      }
    })
  ]

When you are building for development, you may want to use inferno.dev.esm.js ("dev:module": "dist/index.dev.esm.js",) file. That build version has extra level of validation for development purposes. You can use it by adding following code to your webpack config.

    ...
	resolve: {
    /* When doing development workflow we want to make sure webpack picks up development build of inferno */
		alias: {
			inferno: __dirname + "/node_modules/inferno/dist/index.dev.esm.js"
		}
	}

Rollup

Use the following configuration in your Rollup build:

const replace = require('rollup-plugin-replace');
  ...
  plugins: [
    replace({
      'process.env.NODE_ENV': JSON.stringify('production'),
    })
  ]

When you are building for development, you may want to use inferno.dev.esm.js ("dev:module": "dist/index.dev.esm.js",) file. That build version has extra level of validation for development purposes. You can use it by adding following code to your rollup config.

const alias = require('@rollup/plugin-alias');

    ...
  plugins: [
    alias({
        resolve: ['.js'],
        entries: [
          {find: 'inferno', replacement: __dirname + '/node_modules/inferno/dist/index.dev.esm.js'}
        ]
    }),
  ]

Custom namespaces

Inferno always wants to deliver great performance. In order to do so, it has to make intelligent assumptions about the state of the DOM and the elements available to mutate. Custom namespaces conflict with this idea and change the schema of how different elements and attributes might work, so Inferno makes no attempt to support namespaces. Instead, SVG namespaces are automatically applied to elements and attributes based on their tag name.

Development

If you want to contribute code, fork this project and submit a PR from your fork. To run browser tests you need to build the repos. A complete rebuild of the repos can take >5 mins.

$ git clone [email protected]:infernojs/inferno.git
$ cd inferno && npm i
$ npm run test:node
$ npm run build
$ npm run test:browser

Community

There is an Inferno Slack. You can join via inferno-slack.herokuapp.com.

Contributors

This project exists thanks to all the people who contribute. [Contribute].

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

Issues
  • Inferno 3.5.0 and controlled checkboxes and radio

    Inferno 3.5.0 and controlled checkboxes and radio

    Controlled inputs like type='checkbox' or type='radio' generate the onClick events but do not fire onChange events. This is my fault also, I checked the onClick only in https://github.com/AlgoTrader/inferno-controls.

    bug to verify 
    opened by AlgoTrader 54
  • styled-components not work even with inferno-compat?

    styled-components not work even with inferno-compat?

    I'm using inferno-compat, last version, with styled-component and it just not render anything (with any error on console)... Did you know about this? if yes, there is any plan to make it compatible?

    I started to port my app to inferno today, so I just has no ideia if this is a bug or something already expected...

    thanks!

    opened by maxguzenski 52
  • Rendering fragments

    Rendering fragments

    Or in other words, support for components to render multiple children:

    const Component = () => [<Child1 />, <Child2 />];
    

    It was said on slack it's a wanted feature with intention to be implement in future, so I'm creating this issue to have a place to track the progress.

    Someone mentioned that it was already once in Inferno, but at the cost of performance, so it was dropped until a faster implementation is discovered. Was the performance hit really that bad? Because I'd gladly take it if it means the ability to render fragments. Inferno is one of the fastest frameworks out there, so it definitely doesn't lack the perf budget.

    I consider this to be an essential feature to not have DOM polluted with useless wrapper elements which just get in the way of developing, maintaining, and styling components. And React already supports this in their Fiber rewrite, which is mostly done.

    enhancement feature request Fixed in v6.0.0 
    opened by darsain 47
  • New Inferno site design suggestions/mockups

    New Inferno site design suggestions/mockups

    Let's use this thread to aggregate a collection of ideas/notes and mockups for the new InfernoJS website. If you have a design you're working on submit it here for consideration.

    opened by davedbase 47
  • Make compatible with Material-UI

    Make compatible with Material-UI

    Slick material design without bloat vdom library == Material-UI + InfernoJS.

    But:

    ERROR in ./~/react-addons-create-fragment/index.js
    Module not found: Error: Cannot resolve module 'inferno-compat/lib/ReactFragment' in node_modules\react-addons-create-fragment
     @ ./~/react-addons-create-fragment/index.js 1:17-51
    
    ERROR in ./~/react-addons-transition-group/index.js
    Module not found: Error: Cannot resolve module 'inferno-compat/lib/ReactTransitionGroup' in node_modules\react-addons-transition-group
     @ ./~/react-addons-transition-group/index.js 1:17-58
    

    Give me a fix or a workaround.

    enhancement 
    opened by cia48621793 39
  • What's the difference from virtual dom libraries?

    What's the difference from virtual dom libraries?

    Good day!

    Say please, what's the difference from virtual dom libraries making Inferno so fast? Say from virtual-dom...

    Thanks.

    opened by kuraga 38
  • Convert 1.0 codebase to TypeScript

    Convert 1.0 codebase to TypeScript

    Currently the 1.0 codebase lives on the dev branch. It'll gradually be completely converted over to TS – with a keen eye on not reducing any regressions to performance. I'll need community help here (in form of PRs) to help get it all converted.

    Currently the build works fine – it handles the mix of js and ts files and also accounts for the fact that our tests need to use babel for the babel-plugin-inferno to compile JSX code. I'm struggling currently to get all this working properly – npm run test and npm run browser both fail.

    Furthermore, Inferno is using the latest [email protected] for those wondering.

    @Schnueggel any help here would be awesome :)

    enhancement 
    opened by trueadm 36
  • patchComponent: Cannot read property '_unmounted' of null

    patchComponent: Cannot read property '_unmounted' of null

    Observed Behaviour

    Inferno is throwing and uncaught exception Cannot read property '_unmounted' of null. It is happening inside patchComponent when lastVNode.children is null. It is throwing because instance._unmounted is null to be more specific.

    https://github.com/infernojs/inferno/blob/8a605aba148136678f1e7689064b1deb535ac1a5/packages/inferno/src/DOM/patching.ts#L289

    Expected Current Behaviour

    Inferno should not throw an uncaught exception, but should handle null as children appropriately.

    Inferno Metadata

    Using inferno/inferno-compat v1.3.0-rc.8

    macOS / Chrome

    bug help wanted 
    opened by kanzelm3 35
  • Improve the VNode normalization process

    Improve the VNode normalization process

    Background

    Unlike React, Inferno's VNodes are not immutable. They are handled like pseudo-immutable objects in that if multiple instances are detected within Inferno, it attempts to clone the VNode. Inferno does this to reduce object creation and to improve performance (the dom property on VNodes constantly get updated as the mount/patch/unmount process happens during run-time).

    What we currently do

    https://github.com/trueadm/inferno/blob/master/src/core/shapes.ts#L163

    Inferno currently implements a normalization process when you call createVNode. createVNode is the main entry point into creating virtual DOM for Inferno, as such, slowing down this function can have an impact on overall app performance.

    Below explains what the normalization process currently does and what it deals with:

    1. normalizeElement if the type property is a string, but the flags pass through says "Component", Inferno tries to correctly change this a type of "Element". This is done because JSX passes over "Component" when the JSX Element starts with an uppercase name (it assumes all uppercase names are components).

    2. normalizeProps - if the props contains ref, events, children or key, usually because the VNode was created using JSX spread props, we need to put these values back onto the root of the VNode.

    3. normalizeChildren - if the VNode has children, we need to do a bunch of things here (this is generally where the performance impact comes from)

      • we need to assign a property to the children if the children is an array, in this case we assign a property $ directly to the array and set it to true. We use this to know if we've seen this array before. As Inferno's VNodes are not immutable and we use them in the mount/diffing/unmounting, we need to make sure if someone has hoisted the children array, we clone it via children.splice() so we don't mutate the same object.
      • we loop through all children, detecting if we need to flatten children (where there is an array in the children), we check if there is a string or number and convert that to a VNode and if we find a child that has dom already set, we assume it's hoisted and clone it. We do this recursively for all children within children – unless the original children does not need any changes, then we simply return the original children.
      • we do not strip invalid entries from the children or assign pseudo keys to non keyed children (like React does) based on the position of the child in the array. This means that our keyed update process is extremely fragile (see #562).

    Step 3 is causing some issues on performance. It feels like there must be a way to avoid doing this expensive cost if possible. Currently we can avoid normalization in benchmarks by specifying noNormalize via JSX or as a parameter of createVNode which takes away this cost.

    What can we do?

    We need to somehow remove normalisation. If we need to keep it, can we get away with doing it "just in time" during mounting/patching/unmounting to remove this performance loss? It's having an impact on SSR rendering where there is no DOM. It's also having an impact on animations with lots of children that have frequent updates occurring. Yes we can bypass normalization using the flag, but ideally we want to remove this altogether and have a streamlined approach. People using JSX aren't going to know how to use it properly anyway (without breaking their app).

    Any ideas on how we might improve this whilst being able to still handle mixed key children and hoisting of VNodes?

    @localvoid @thysultan @Havunen

    enhancement 
    opened by trueadm 32
  • What is the roadmap ?

    What is the roadmap ?

    Hi, @trueadm

    Seems great this project, but comparing to the readme. A couple of missing pieces?

    • createElement(). Is this something coming soon? I think that will give you even more stars. I was looking into the code, and shouldn't be too hard to copy from your very great t7 script? Or maybe I'm wrong.
    • different things seems unfinished inside the code, any plans for finishing this?
    • any plans for hooks ala Snabbdom? Not lifecycle, but example when you create a fragment, you can trigger a callback, same when you remove or update a fragment.
    • Server side rendring, is this going to happen soon? It's more or lest a must have if I should convert to Inferno. I'm from React world!

    Btw. Is there any benchmark for latest version, and what is the roadmap?

    I will absolutly start to use this script soon as a createElement() are done. And I like your component part too :+1:

    opened by ghost 31
  • SSR tests are run in JSDOM env and rely on document

    SSR tests are run in JSDOM env and rely on document

    Observed Behaviour

    All server rendering tests are run with JSDOM-environment exposing document which isn't available in node during SSR.

    Expected Current Behaviour

    We should run *.spec.server.jsx with separate config file and testEnvironment: "node"

    opened by jhsware 0
  • issue or feature shallowDiffers inferno

    issue or feature shallowDiffers inferno

    just was a look in the code of preact it there some change in shallow

    https://github.com/preactjs/preact/commit/de388d2066df632b10c57644b9643164a39ff426

    function shallowDiffers(a, b) {
    	- for (let i in a) if (!(i in b)) return true;
    	- for (let i in b) if (a[i]!==b[i]) return true;
    	+ for (let i in a) if (i !== '__source' && !(i in b)) return true;
    	+ for (let i in b) if (i !== '__source' && a[i]!==b[i]) return true;
    	return false;
    }
    
    opened by simonjoom 1
  • Question: migrating react app to inferno

    Question: migrating react app to inferno

    Hey,

    So I have a react app that I'd like to migrate to inferno for performance reasons. I spent a few hours trying to configure my (ejected) create-react-app to use inferno but wasn't successful. I was wondering if there was a guide of all the points to be careful of to do the migration? I was also wondering if it's thinkable to port an app using React hooks via xferno, described in #1453.

    Thanks.

    question 
    opened by romgrk 3
  • [inferno-test-utils] How to use this lib to change state or props, trigger change/input event/keydown event?

    [inferno-test-utils] How to use this lib to change state or props, trigger change/input event/keydown event?

    When I use inferno-test-utils lib to test my inferno app, I encounter some problems that need your help. Firstly I rendered a component use renderIntoContainer.

    But I have some problems blocks my work.

    1. How to get this rendered instance that I can get the global variables bound component?
    2. How can I change state/props in a test suite so that improving code coverage?
    3. How can I manually trigger input/change events in a test suite when I test the input element?

    Look forward to your replying. Thanks.

    opened by ReginaLiang 1
  • [inferno-test-utils] renderIntoContainer can't render mocked component inner children.

    [inferno-test-utils] renderIntoContainer can't render mocked component inner children.

    Reproduce steps:

    I have a component as follow:

    export default function TextView(props) {
      return (
        <Overlay>
          <div className={styles.container}>
            <div className={styles.header} data-l10n-id="scann-dialog-title-text" />
            <div ref={elem => props.onRef(elem)} className={styles.body}>
              {props.text}
            </div>
          </div>
        </Overlay>
      );
    }
    

    when I tested this component with jest. I mocked Overlay component.

    jest.mock("./components", () => {
      return {
        Overlay: ({ className, style, children }) => {
          return (<div id={"mockedOverlayComponent"}>{children}</div>);
        }
      };
    });
    

    then using renderIntoContainer to render TextView.

    const renderedTree = renderIntoContainer(<TextView {...props} />);

    I expect renderedTree.dom is instance of HTMLElement. Actually, renderedTree.dom is null.

    PS: But when I use render from inferno to render TextView.

    const render = require('inferno').render;
    const renderedTree = render(<TextView {...props} />, dom);
    

    the renderedTree.dom is domElement, children is correctly render, the final result is:

    <div id="mockedOverlayComponent">
        <div class="container">
            <div class="header" data-l10n-id="scann-dialog-title-text" />
            <div class="body"> testText </div>
        </div>
    </div>
    

    So, I think maybe renderIntoContainer method has some problems. Please help to deal with this issue.

    Looking forward to your reply. Thanks.

    bug to verify 
    opened by ReginaLiang 1
  • Inferno with TypeScript ignores `defaultProps` in JSX

    Inferno with TypeScript ignores `defaultProps` in JSX

    Observed Behaviour

    Inferno with TypeScript ignores defaultProps in JSX. Error: Property 'value' is missing in type '{}' but required in type 'ComponentPropsType'. See Inferno example: https://codesandbox.io/s/inferno-ts-example-i0i2c?file=/src/App.tsx.

    Expected Current Behaviour

    Inferno with TypeScript should notice defaultProps in JSX, like React. See React example: https://codesandbox.io/s/react-ts-example-2zezs?file=/src/App.tsx.

    Inferno Metadata

    Inferno v7.4.7

    bug Typescript 
    opened by LazyLahtak 1
  • provide a esbuild workflow

    provide a esbuild workflow

    Before submitting an issue please:

    • Check that you are using the latest version of Inferno. Either using our CDN @ Master or by checking the tags on NPM.
    • Check that the bug has not been fixed in the latest development version. Use our CDN @ Edge.
    • Check that the issue has not been brought up before on Github issues.

    If you can, please distill your problem down and include a JSFiddle example for illustration. Also when requesting bug fix please include at least one test to avoid regression.

    Issue Template

    Observed Behaviour

    Inferno is...

    Expected Current Behaviour

    Inferno should...

    Inferno Metadata

    macOS / Windowx / Linux Safari / Chrome / Firefox / ...

    question documentation 
    opened by deleonio 2
  • Use `== null` instead of `isNullOrUndef`?

    Use `== null` instead of `isNullOrUndef`?

    More of a question than an issue; why is inferno using isNullOrUndef in inferno-shared instead of just using == null? Ran a benchmark (https://www.measurethat.net/Benchmarks/Show/6389/0/compare-comparison-with-null-or-undefined) and == null seems to be 3 times quicker than === null || === undefined in all browsers I tested. Is it because of byte savings?

    enhancement Investigation 
    opened by joseprio 3
  • Preferred / better typescript build system for inferno (parcel, rollup) ?

    Preferred / better typescript build system for inferno (parcel, rollup) ?

    I'm the front end dev for Lemmy, and we're using @deamme 's typescript transformer, along with fuse-box, to do our front end builds.

    Unfortunately tho, fuse-box has upgraded to a new version, and it doesn't seem to support inferno (I tried and failed at adapting it).

    Although fuse-box v3 is currently working, we do want to stay with something that's going to be supported in the future, and does all the necessary uglifying and stripping that fuse-box does.

    Parcel and Rollup.js seem like good possibilities: https://blog.bitsrc.io/choosing-the-right-javascript-bundler-in-2020-f9b1eae0d12b

    question documentation 
    opened by dessalines 4
  • @material-ui/core ^4.9.5 'memo' is not exported from 'react'

    @material-ui/core ^4.9.5 'memo' is not exported from 'react'

    Using:

      "dependencies": {
        "@material-ui/core": "^4.9.5",
        "inferno": "^7.4.2",
        "inferno-compat": "^7.4.2",
        "inferno-scripts": "7.0.4"
      }
    

    got:

    Attempted import error: 'memo' is not exported from 'react' (imported as 'React').
    

    App.js

    import { version, Component } from 'inferno';
    import MaterialButton from '@material-ui/core/Button';
    import Logo from './logo';
    import './App.css';
    
    class App extends Component {
      render() {
        return (
          <div className="App">
            <header className="App-header">
              <Logo width="80" height="80" />
              <p>{`Welcome to Inferno ${version}`}</p>
              <p>
                Edit <code>src/App.js</code> and save to reload.
              </p>
              <MaterialButton
                variant="outlined"
                color="primary"
              >TEST</MaterialButton>
            </header>
          </div>
        );
      }
    }
    
    export default App;
    
    opened by aeroxy 1
Releases(v8.0.0-alpha.3)
  • v8.0.0-alpha.3(Nov 24, 2021)

    Inferno

    • Removes development bundle warning when infernojs is used in Jest test environment https://github.com/infernojs/inferno/commit/5c017e189c67875516145f3efb56b0a8e6d124f3
    • Fixes an issue where context becomes null when fragment is used to render single vNode https://github.com/infernojs/inferno/commit/ef07f26bbca0359e61c302f8c566bfb98da07724

    Inferno-animations

    • New feature global animations https://github.com/infernojs/inferno/commit/776b607573445a8891d8c9a11dee2e2ca791a0c2
    Source code(tar.gz)
    Source code(zip)
  • v7.4.11(Nov 3, 2021)

    • Fixes an issue where top level context becomes null if Fragment was rendered having single child node https://github.com/infernojs/inferno/issues/1579
    Source code(tar.gz)
    Source code(zip)
  • v8.0.0-alpha.2(Nov 3, 2021)

  • v8.0.0-alpha.1(Oct 25, 2021)

    • inferno-component package has been removed. Component is available in "inferno" main package
    • inferno-animation clean up and performance bug fixes: https://github.com/infernojs/inferno/pull/1575 https://github.com/infernojs/inferno/pull/1576
    • internal dependencies updated
    Source code(tar.gz)
    Source code(zip)
  • v8.0.0-alpha.0(Sep 22, 2021)

    New package inferno-animation has been added

    Inferno-router

    "history" package has been updated to the latest major version 5

    Multiple internal changes to build system and dependencies

    Note

    This is preview release available for testing and there might be breaking changes in future releases

    Source code(tar.gz)
    Source code(zip)
  • v7.4.10(Sep 11, 2021)

    All packages

    This release fixes a possible supply chain attack by adding repository link to all packages https://github.com/infernojs/inferno/pull/1574

    Source code(tar.gz)
    Source code(zip)
  • v7.4.9(Aug 21, 2021)

    Inferno-core

    • Adds typing support for lazy loading images https://github.com/infernojs/inferno/commit/e34e287d60855e750b002140660e7ef72d6c4204
    • Fixes an issue where normalizeProps overrides explicitly defined class name property https://github.com/infernojs/inferno/commit/592e065d3ed19d86e642004d9cea47089b908738

    Inferno-router

    • Adds typing support for title and other html element attributes to Link component https://github.com/infernojs/inferno/commit/6480b05709c32f5b249e9807b3a7da24e53e7fe2
    Source code(tar.gz)
    Source code(zip)
  • v7.4.8(Feb 14, 2021)

    Inferno core

    Fixes an issue where shouldComponentUpdate gets called after forceUpdate if there were pending state changes on the given component https://github.com/infernojs/inferno/issues/1534 https://github.com/infernojs/inferno/pull/1535 Inernal dependencies updated

    Source code(tar.gz)
    Source code(zip)
  • v7.4.7(Jan 13, 2021)

    Inferno-core

    This release fixes wrong "latest" tag in npm registry after v5 hotfix Internal dependencies updated https://github.com/infernojs/inferno/commit/90e2daadf059f00e2ea8ea35a38efe00d037491e License year updated https://github.com/infernojs/inferno/commit/1f06cdd90bf6bdc63eb7e72c1ea7e4086d12f2d7

    Source code(tar.gz)
    Source code(zip)
  • v5.6.2(Jan 13, 2021)

    Inferno Core

    This is patch inferno v5x versions to change opencollective dependency to opencollective postinstall. Closes https://github.com/infernojs/inferno/issues/1532 original change backported: https://github.com/infernojs/inferno/commit/0ea17d05dcded3aa187065ea852ce68f6f6c14ac

    Source code(tar.gz)
    Source code(zip)
  • v7.4.6(Oct 22, 2020)

  • v7.4.5(Sep 19, 2020)

    Inferno-core

    Improved createRef() type

    Inferno-server

    Fixes a bug where rendering forwardRef component server side failed to exception. https://github.com/infernojs/inferno/issues/1523

    Source code(tar.gz)
    Source code(zip)
  • v7.4.4(Sep 19, 2020)

    Inferno-router

    Navlink component typescript typings have been improved and it does not require all properties to be set anymore. This fixes Github issue https://github.com/infernojs/inferno/issues/1518

    Internal dependencies were updated

    Source code(tar.gz)
    Source code(zip)
  • v7.4.3(Aug 21, 2020)

    Inferno core

    Optimized rendering functional component https://github.com/infernojs/inferno/commit/1af165f3875d8ccca20def1ee7835012508d3616 Optimized cloneFragment method https://github.com/infernojs/inferno/commit/85eba1228411bcb572f0382d84a7f39cc23689c2

    Internal development dependencies have been upgraded

    Source code(tar.gz)
    Source code(zip)
  • v7.4.2(Mar 2, 2020)

    Inferno core

    Fixes an issue introduced in v7.4.1 where setState callback was called even if component got unmounted https://github.com/infernojs/inferno/commit/0e6b2438bac4539a97c4debe97cbda8c07703b28

    Source code(tar.gz)
    Source code(zip)
  • v7.4.1(Feb 25, 2020)

    Inferno core

    Fixes an issue where all setState callbacks were not called after chaining multiple setStates during asynchronous flow

    Inferno router

    Fixes typings of IRouteProps component https://github.com/infernojs/inferno/commit/078b323b0c63f5fc40d9a3bc0aaedc7a24031880

    Source code(tar.gz)
    Source code(zip)
  • v7.4.0(Jan 28, 2020)

    Inferno-server

    • Adds support for rendering array from Component root. https://github.com/infernojs/inferno/commit/9396adea5b86849a8afd28bb150ae46a78327cff

    Inferno-compat

    • Removed always truthy conditions from Children methods https://github.com/infernojs/inferno/commit/fb9d5febddb0c8a0cef97c58c681d2dcdf50baa2
    Source code(tar.gz)
    Source code(zip)
  • v7.3.3(Nov 19, 2019)

  • v7.3.2(Oct 8, 2019)

  • v7.3.1(Aug 22, 2019)

    Inferno-hydration

    • Fixes an issue where hydrating forwardRef Component crashed https://github.com/infernojs/inferno/issues/1486 https://github.com/infernojs/inferno/commit/646753c70c87c3a425bea100126a35aef25751da
    Source code(tar.gz)
    Source code(zip)
  • v7.3.0(Aug 13, 2019)

    Inferno-core

    • Adds root level array support to createPortal
    • Synthetic events are now propagated from shadow-dom https://github.com/infernojs/inferno/issues/1430 This requires browser to support shadow-dom https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_shadow_DOM
    • Code clean up
    Source code(tar.gz)
    Source code(zip)
  • v7.2.1(Jul 25, 2019)

    Inferno-core

    • Fixes an issue caused by Release 7.2.0 where events were not updated correctly https://github.com/infernojs/inferno/commit/be677f9a3d096a44b8116581211ccb2e8de8518c
    • Simplified and optimized Synthetic event patch routines
    Source code(tar.gz)
    Source code(zip)
  • v7.2.0(Jul 24, 2019)

    Inferno-core

    • Adds support for defaultHooks when using forwardRef functional components
    • Fixes performance regression between 7.0.2 and 7.1.13

    General

    • All dependencies updated
    • UglifyJS has been replaced with TerserJS
    Source code(tar.gz)
    Source code(zip)
  • v7.1.13(May 30, 2019)

    Inferno-core

    • Fixes a bug where extending forwardRef component was not possible https://github.com/infernojs/inferno/issues/1473

    Inferno-devtools

    • Fixes a bug where inferno-devtools did not start https://github.com/infernojs/inferno/issues/1479
    Source code(tar.gz)
    Source code(zip)
  • v7.1.12(Apr 24, 2019)

    Inferno core

    • Fixes an issue where value of Inferno.createRef() did not update correctly https://github.com/infernojs/inferno/issues/1465 https://github.com/infernojs/inferno/pull/1466
    • Fixes an issue where <select> element selectIndex attribute was rendered to DOM https://github.com/infernojs/inferno/pull/1468
    Source code(tar.gz)
    Source code(zip)
  • v7.1.11(Mar 24, 2019)

    Inferno-core

    • Adds feature to silent lifecycle deprecation messages https://github.com/infernojs/inferno/pull/1461 https://github.com/infernojs/inferno/issues/1458

    Example:

        class Foo extends Component {
            // just added to force the warnings
            static getDerivedStateFromProps() { }
    
             componentWillMount() { }
    
             componentWillReceiveProps() { }
    
             componentWillUpdate() { }
    
             render() {
                 return <div>Foo</div>;
             }
        }
    
        Foo.prototype.componentWillMount.__suppressDeprecationWarning = true;
        Foo.prototype.componentWillReceiveProps.__suppressDeprecationWarning = true;
        Foo.prototype.componentWillUpdate.__suppressDeprecationWarning = true;
    
    Source code(tar.gz)
    Source code(zip)
  • v7.1.10(Mar 11, 2019)

    Inferno-test-utils

    Removed props.children from snapshot when using inferno-compat. Fixes https://github.com/infernojs/inferno/issues/1451

    Source code(tar.gz)
    Source code(zip)
  • v7.1.9(Feb 20, 2019)

    Inferno core

    • Changed opencollective script to use opencollective-postinstall package to reduce inferno package size https://github.com/infernojs/inferno/issues/1450
    Source code(tar.gz)
    Source code(zip)
  • v7.1.8(Feb 19, 2019)

  • v7.1.7(Feb 11, 2019)

JavaScript and TypeScript finite state machines and statecharts for the modern web.

JavaScript state machines and statecharts JavaScript and TypeScript finite state machines and statecharts for the modern web. ?? Read the documentatio

Stately 18.1k Nov 28, 2021
Facebook components like a Login button, Like, Share, Chat, Comments, Page or Embedded Post

React Facebook Components Components Facebook provider (provide settings to child components) Login button (provide user profile and signed request) L

Zlatko Fedor 704 Nov 22, 2021
A javascript framework to share url to social media sites like facebook, twitter, reddit, whastapp in an easy and simple way.

simple-sharer [by BUILDBROTHERS.COM] A javascript framework to share url to social media sites like facebook, twitter, reddit, whastapp in an easy and

null 2 Nov 30, 2021
Node.js library for building systematic trading strategies in reactive way.

Node.js library for building systematic trading strategies in reactive way. Use the power of TypeScript and Reactive Programming to research, develop

null 2 Nov 24, 2021
An algebraic effects library for javascript and typescript using generators

Algebraify Algebraic Effects Are Here! (sort of) (If you're unfamiliar with algebraic effects, here's a great article: Algebraic Effects for the Rest

Jackie Edwards 9 Nov 23, 2021
The history library lets you easily manage session history anywhere JavaScript runs.

history · The history library lets you easily manage session history anywhere JavaScript runs. A history object abstracts away the differences in vari

Remix 7.4k Dec 2, 2021
User-friendly query builder for React

react-awesome-query-builder User-friendly React component to build queries. Inspired by jQuery QueryBuilder Using awesome Ant Design v4 for widgets No

Denis Oblogin 1k Dec 2, 2021
React project with Google Firebase API, create partys with admin view and user view. Users can ask topics to admin, and support other topics.

?? Tecnologias Esse projeto foi desenvolvido com as seguintes tecnologias: React Firebase TypeScript ?? Como executar Clone o projeto e acesse a pasta

Felipe Souza 3 Aug 27, 2021
TSDX React w/ Storybook User Guide

TSDX React w/ Storybook User Guide Congrats! You just saved yourself hours of work by bootstrapping this project with TSDX. Let’s get you oriented wit

Achraf 1 Nov 11, 2021
Generate fun kaleidoscope for user avatars.

React Avatar Generator This was inspired by an old website called LayerVault. You can see an example of how that used to look like here. Getting Start

Joseph Smith 38 Nov 28, 2021
Consuming GitHub API, showing user's profile and repositories, with ReactJS

GitHubProfiles Project made with ReactJS to practice API consuming using GitHub API, in order to show in a simple way user's profile and repositories.

Hugo Ferreira 5 Sep 11, 2021
Generate GitBook style modern docs/tutorial websites using Gatsby + MDX

gatsby-gitbook-starter Kick off your project with this starter to create a powerful/flexible docs/tutorial web apps. Motivation We wanted to create a

Vaishnavi Dwivedi 3 Nov 21, 2021
React ESI: Blazing-fast Server-Side Rendering for React and Next.js

React ESI: Blazing-fast Server-Side Rendering for React and Next.js React ESI is a super powerful cache library for vanilla React and Next.js applicat

Kévin Dunglas 592 Nov 24, 2021
Fast Touch Events for React

React Fastclick Instantly make your desktop / hybrid apps more responsive on touch devices. React Fastclick automatically adds fastclick touch events

Jake 'Sid' Smith 481 Sep 2, 2021
A starter for React with Typescript with the fast Vite and all static code testing with Eslint and formatting with Prettier.

A starter for React with Typescript with the fast Vite and all static code testing with Eslint and formatting with Prettier.

The Sword Breaker 79 Nov 20, 2021
An interactive CLI automation tool 🛠️ for creating react.js and next.js projects most fast and efficiently. ⚛️

An interactive CLI automation tool ??️ for creating react.js and next.js projects most fast and efficiently. ⚛️

Alexis Guzman 26 Nov 9, 2021
A curated list of resources to learn React and related web technologies as fast as possible.

React Learning Resources A curated list of resources to learn React and related web technologies as fast as possible. The goal is to help you create p

Naresh Bhatia 25 Nov 7, 2021
🦁 <1kb compiler-augmented virtual DOM. It's fast!

English | 中文 <1kb compiler-augmented virtual DOM. It's fast! Current Virtual DOM implementations are inadequate—Ranging from overcomplicated to abando

Aiden Bai 1.3k Nov 21, 2021
The react UI component for building complex filter criteria

React Filter Control The React component for building the composite filter criteria Demo (JS) | Demo (TS) Together With Data Table Overview Installati

Alexander Komarov 29 Jul 24, 2021