Feature request: export scripts (start/test/build) as functions

[tuchk4]

TLDR
very very simple example:

const start = require('react-scripts/scripts/start');
const config = require('react-scripts/config/weback.config.dev');
start(config);

An same for test / build.

Change webpack config  —  add plugins and change entry point

I have two situation when I have to do this:

• Add Webpack Offline Plugin.
• Publish single component as the separated build. (Seems related to How to publish components without ejecting #796)

Another case - start or build Create React Application from another node script. Right now it is possible with spawn:

const start = spawn('node', ['neutron-server/start.js'], {
  cwd: path.join(__dirname, '..'),
  stdio: 'inherit'
});

With suggest feature this should be more beautiful.

---

There is the workaround how to implement it. I wrote about it at Why I love Create React App

Add build:custom to npm-scripts:

"scripts": {
  "build:custom": "node scripts/webpack"
}

And then create scripts/webpack.js:

const webpack = require('react-scripts/node_modules/webpack');
const craWebpackConfig = require('react-scripts/config/webpack.config.prod');
const OfflinePlugin = require('offline-plugin');

const config = {
  ...craWebpackConfig,
  plugins: [
     ...craWebpackConfig.plugins,
     new OfflinePlugin()
  ],
  entry: [
    craWebpackConfig.entry[0], // pollyfils
    path.resolve('src', 'awesome-component.js')
  ],
  output: {
    ...craWebpackConfig.output,
    path: path.resolve('pf-build')
  }
};
webpack(config).run(function(err, stats) {
  if (err !== null) {
    console.log('done');
  } else {
    console.log(err);
  }
});

There is just webpack config extending, not react-scripts build. And there are no beautiful console logs, comparison of the build sizes and other react-scripts build command features.
With suggested feature - it is possible to use start/test/build scripts but with custom configs.

[gaearon]

We don't plan to expose Webpack config. That CRA uses Webpack is an implementation detail. If something that fits our use case better comes along, we will switch to that instead, and we don't want this to be a burden to our users. Therefore we don't intend to make Webpack usage explicit until you eject.

[tuchk4]

I expected such your answer :)
But anyway decided to request the feature. At medium post Why I love Create React App I tried to describe why I love CRA and why I don't want to eject.

[gaearon]

I'm happy to consider feature requests on case by case basis. For example I think we could enable OfflinePlugin by default. I just don't know enough about it so I have been postponing this until a later stage.