custom-react-scripts

Modify the .env file in the root of the generated project, and add any of the configuration options to enable that feature. The generated project comes with every option turned on by default, but you can remove them at any time by removing the options from the .env file. Add a .env. file with the desired features. Files that are not prefixed with the module will be parsed normally. Some of the babel presets and plugins that people might use are experimental. If they're used in a project and then they don't make it in the ES spec, they will break backward compatibility. It's hard to maintain code for all of these custom configurations that people want to use. So instead of searching npm for a react-scripts fork with the X feature you need, this fork provides support for all of these extra features by simply adding a line in the .env config. The CRA team recently added support for an .env file at the root of the generated CRA project.