overridable-react-scripts

This package includes scripts and configuration used by Create React App. Please refer to its documentation:

• Getting Started – How to create a new app.
• User Guide – How to develop apps bootstrapped with Create React App.

Quick Start

To create a project called my-app, run this command:

npx create-react-app my-app --scripts-version overridable-react-scripts

How to override configs ?

In your project's root you'll find react-scripts.override.js which contains functions that could mutate the paths/webpack/webpackDevServer configuration provided by create-react-app.

If you started project with official react-scripts, you should insert this file into the project's root folder:

react-scripts.override.js

/**
 * Function to override paths
 *
 * @param {Object} paths - object contains paths for webpack and other scripts
 * @param {Object} options
 * @param {Function} options.resolveApp - function, which resolve path relative to app directory
 */
function overridePaths(paths, options) {
  return paths;
}

/**
 * Function to override webpack config
 *
 * @param {Object} webpackConfig - webpack config
 * @param {Object} options
 * @param {Object} options.webpack - webpack instance
 * @param {Object} options.paths - object of paths
 * @param {String} options.webpackEnv - "development" or "production"
 */
function overrideWebpackConfig(webpackConfig, options) {
  return webpackConfig;
}

/**
 * Function to override Webpack Dev Server config
 *
 * @param {Object} webpackDevServerConfig - webpack dev server config
 * @param {Object} options
 * @param {Object|Function} options.proxy - proxy config ( https://webpack.js.org/configuration/dev-server/#devserver-proxy )
 * @param {Object} options.allowedHost - public url of dev server ( https://webpack.js.org/configuration/dev-server/#devserver-public )
 */
function overrideWebpackDevServerConfig(webpackDevServerConfig, options) {
  return webpackDevServerConfig;
}

module.exports = {
  overridePaths,
  overrideWebpackConfig,
  overrideWebpackDevServerConfig
};

Multiple env configs for production build

Create React App allow only one .env.production config for NODE_ENV="production". But this fork lets to create multiple .env files for production builds.

Create React App uses variable NODE_ENV to find env file, but this fork uses env ENV_FILE for these purposes. For example, if you set ENV_FILE=stage, webpack will use .env.stage env file. If you don't set ENV_FILE variable, NODE_ENV will be used by default. You can install cross-env package to set and use environment variables across platforms.

Example of npm scripts in package.json

"scripts": {
  "start": "react-scripts start",
  "build:stage": "cross-env ENV_FILE=stage react-scripts build",    // <-- .env.stage
  "build:production": "cross-env ENV_FILE=production react-scripts build",    // <-- .env.production
  "test": "react-scripts test",
  "eject": "react-scripts eject"
},

Which version of react-scripts does this fork use ?

You can find config version at the field react-scripts-version of package.json.