babel-plugin-transform-react-remove-prop-types

Remove unnecessary React propTypes from the production build.

Installation

1npm install --save-dev babel-plugin-transform-react-remove-prop-types

The problem solved

Remove React propTypes from the production build, as they are only used in development. You can save bandwidth by removing them.

Example

In

1const Baz = (props) => (
2  <div {...props} />
3);
4
5Baz.propTypes = {
6  className: PropTypes.string
7};

Out

1const Baz = (props) => (
2  <div {...props} />
3);

With comment annotation

The majority of cases should be addressed by default by this plugin.

In some cases, for example when using HOCs (High Order Components), like react-redux's connect, or component inheritance (although it's NOT recommended), a comment after the propTypes definition may be used to force the removal:

1Component.propTypes /* remove-proptypes */ = {}

Usage

Via .babelrc (Recommended)

.babelrc

without options:

1{
2  "env": {
3    "production": {
4      "plugins": ["transform-react-remove-prop-types"]
5    }
6  }
7}

with options:

1{
2  "env": {
3    "production": {
4      "plugins": [
5        ["transform-react-remove-prop-types", {
6          "mode": "wrap",
7          "ignoreFilenames": ["node_modules"]
8        }]
9      ]
10    }
11  }
12}

Via CLI

1babel --plugins transform-react-remove-prop-types script.js

Via Node API

without options:

1require('babel-core').transform('code', {
2  plugins: [
3    'transform-react-remove-prop-types',
4  ],
5});

with options:

1require('babel-core').transform('code', {
2  plugins: [
3    [
4      'transform-react-remove-prop-types',
5      {
6        mode: 'wrap',
7        ignoreFilenames: ['node_modules'],
8      },
9    ],
10  ],
11});

Options

mode

• remove (default): the propTypes definitions are removed from the source code.
• wrap: the propTypes definitions are wrapped with the following code:

1Component.propTypes = process.env.NODE_ENV !== "production" ? {
2  // ...
3} : {};

Accessing Component.propTypes.className won't throw. It's a tradeoff between the size of the output file and the likelihood libraries like react-native-hyperlink breaks.

• unsafe-wrap: the propTypes definitions are wrapped with the following code:

1if (process.env.NODE_ENV !== "production") {
2  Component.propTypes = {
3    // ...
4  }
5}

Accessing Component.propTypes.className will throw.

The wrap modes are targeting React libraries like material-ui or react-native-web. They are not intended to be used by application authors.

removeImport

• true: the import statements are removed as well. This option only works if mode is set to remove:

1import PropTypes from 'prop-types'

• false (default): does not remove the import statements.

ignoreFilenames

This filter generates a regular expression. Any filenames containing one of the array's strings will be ignored. By default, we match everything.

Following the Is it safe? section, you might encounter a component depending on the propTypes at runtime to work. For this reason, we provide an array options to filter out some files and folders. For instance, you can ignore all the npm modules:

1ignoreFilenames: ['node_modules'],

additionalLibraries

This option gives the possibility to remove other propTypes in addition to the canonical prop-types.

For instance, by default

1import PropTypes from 'prop-types'
2import ImmutablePropTypes from 'react-immutable-proptypes'

will result in the latter not to be removed, while with:

1additionalLibraries: ['react-immutable-proptypes'],

both will be removed.

Regular expressions

If you are using Babel 7 or newer and your config is stored in babel.config.js, you can also use a regular expression to describe modules, which should be removed.

This would be particularly useful when using custom prop types validators, implemented as part of your own source code. For example

1import CustomPropTypes from '../../prop-types/my-own-validator'
2import OtherCustomPropTypes from '../../prop-types/my-other-validator'

would be removed with the following setting

1additionalLibraries: [/\/prop-types\/.*$/]

If you use an index file

1import CustomPropTypes from '../../prop-types'

you could set it up as

1additionalLibraries: [/\/prop-types$/]

classNameMatchers

Use this option to enable this plugin to run on components that extend a class different than React.Component or React.PureComponent.

Given this example:

1class MyComponent extends BaseComponent {
2  ...
3}

You would use:

1classNameMatchers: ["BaseComponent"]

createReactClassName

Use this option to set a custom name for the import of the create-react-class package that is different than createReactClass.

Given this example:

1import createClass from 'create-react-class';

You would use:

1createReactClassName: 'createClass'

Is it safe?

If you are using the propTypes in a conventional way, i.e by using them to perform type checking on the properties, that plugin should be safe to use.

However, some libraries are accessing the propTypes on the component directly. For instance react-native-vector-icons use them to split the properties between two components:

1const touchableProps = pick(restProps, Object.keys(TouchableHighlight.propTypes));

:warning: The plugin is breaking that code if it ends up removing TouchableHighlight.propTypes.

Make sure you are:

• Not using that pattern in your source code. If you do, explicitly export the propTypes to work around that limitation.
• Not parsing the node_modules. If you do, test that your code is still working before shipping into production.

eslint-plugin-react has a rule forbid-foreign-prop-types that can help you make this plugin safer to use.

License

MIT