@babel/plugin-transform-react-inline-elements

Note

When used alongside @babel/plugin-transform-runtime, polyfills (by default including Symbol) are specifically scoped to not pollute the global scope. This breaks usage with React, as it won't have access to that polyfill and will cause your application to fail in legacy browsers.

Even if ['@babel/plugin-transform-runtime', { helpers: true, polyfill: false }] is specified, it might still break, since helpers come precompiled.

In this case, we recommend importing/requiring @babel/polyfill in the entry point of your application and using @babel/preset-env with the useBuiltIns option to only include the polyfills your targets need. Alternatively, you can also import/require core-js/modules/es6.symbol by itself.

This transform should be enabled only in production (e.g., just before minifying your code) because, although it improves runtime performance, it makes warning messages more cryptic and skips important checks that happen in development mode, including propTypes.

Example

In

  1. <Baz foo="bar" key="1"></Baz>;

Out

  1. babelHelpers.jsx(Baz, {
  2. foo: "bar"
  3. }, "1");
  4. /**
  5. * Instead of
  6. *
  7. * React.createElement(Baz, {
  8. * foo: "bar",
  9. * key: "1",
  10. * });
  11. */

Deopt

  1. // The plugin will still use React.createElement when `ref` or `object rest spread` is used
  2. <Foo ref="bar" />
  3. <Foo {...bar} />

Installation

  1. npm install --save-dev @babel/plugin-transform-react-inline-elements

Usage

.babelrc

  1. {
  2. "plugins": ["@babel/plugin-transform-react-inline-elements"]
  3. }

Via CLI

  1. babel --plugins @babel/plugin-transform-react-inline-elements script.js

Via Node API

  1. require("@babel/core").transform("code", {
  2. plugins: ["@babel/plugin-transform-react-inline-elements"]
  3. });

References