Advanced Configuration

Advanced Configuration

You can adjust various development and production settings by setting environment variables in your shell or with .env.

Note: You do not need to declare REACTAPP before the below variables as you would with custom environment variables.

Variable	Development	Production	Usage
BROWSER	✅ Used	🚫 Ignored	By default, Create React App will open the default system browser, favoring Chrome on macOS. Specify a browser to override this behavior, or set it to `none` to disable it completely. If you need to customize the way the browser is launched, you can specify a node script instead. Any arguments passed to `npm start` will also be passed to this script, and the url where your app is served will be the last argument. Your script's file name must have the `.js` extension.
BROWSERARGS	✅ Used	🚫 Ignored	When the `BROWSER` environment variable is specified, any arguments that you set to this environment variable will be passed to the browser instance. Multiple arguments are supported as a space separated list. By default, no arguments are passed through to browsers.
HOST	✅ Used	🚫 Ignored	By default, the development web server binds to `localhost`. You may use this variable to specify a different host.
PORT	✅ Used	🚫 Ignored	By default, the development web server will attempt to listen on port 3000 or prompt you to attempt the next available port. You may use this variable to specify a different port.
HTTPS	✅ Used	🚫 Ignored	When set to `true`, Create React App will run the development server in `https` mode.
PUBLIC_URL	🚫 Ignored	✅ Used	Create React App assumes your application is hosted at the serving web server's root or a subpath as specified in `package.json` (`homepage`). Normally, Create React App ignores the hostname. You may use this variable to force assets to be referenced verbatim to the url you provide (hostname included). This may be particularly useful when using a CDN to host your application.
CI	✅ Used	✅ Used	When set to `true`, Create React App treats warnings as failures in the build. It also makes the test runner non-watching. Most CIs set this flag by default.
REACT_EDITOR	✅ Used	🚫 Ignored	When an app crashes in development, you will see an error overlay with clickable stack trace. When you click on it, Create React App will try to determine the editor you are using based on currently running processes, and open the relevant source file. You can send a pull request to detect your editor of choice. Setting this environment variable overrides the automatic detection. If you do it, make sure your systems [PATH](https://en.wikipedia.org/wiki/PATH(variable)) environment variable points to your editor’s bin folder. You can also set it to `none` to disable it completely.
CHOKIDAR_USEPOLLING	✅ Used	🚫 Ignored	When set to `true`, the watcher runs in polling mode, as necessary inside a VM. Use this option if `npm start` isn't detecting changes.
GENERATE_SOURCEMAP	🚫 Ignored	✅ Used	When set to `false`, source maps are not generated for a production build. This solves out of memory (OOM) issues on some smaller machines.
NODE_PATH	✅ Used	✅ Used	Same as `NODE_PATH` in Node.js, but only relative folders are allowed. Can be handy for emulating a monorepo setup by setting `NODE_PATH=src`.
INLINE_RUNTIME_CHUNK	🚫 Ignored	✅ Used	By default, Create React App will embed the runtime script into `index.html` during the production build. When set to `false`, the script will not be embedded and will be imported as usual. This is normally required when dealing with CSP.
IMAGE_INLINE_SIZE_LIMIT	🚫 Ignored	✅ Used	By default, images smaller than 10,000 bytes are encoded as a data URI in base64 and inlined in the CSS or JS build artifact. Set this to control the size limit in bytes. Setting it to 0 will disable the inlining of images.
EXTEND_ESLINT	✅ Used	✅ Used	When set to `true`, ESLint configs that extend `eslint-config-react-app` will be used by `eslint-loader`. Any rules that are set to `"error"` will stop the application from building.