Commits on Sep 14, 2018

1. Lazily require() webpack plugins to improve performance …

   webpack-chain 4.11.0's `.plugin('abc').use(...)` now supports being
   passed the path to a plugin, instead of the plugin itself. See:
   neutrinojs/webpack-chain#102
   
   This means we can avoid the expensive `require()` of plugins in cases
   where the plugin isn't used - such as when:
   * running ESLint's CLI with a Neutrino-generated `.eslintrc.js`
   * running tests with Jest/Mocha (which don't perform a webpack build)
   * the plugin isn't needed for that `NODE_ENV` (eg `clean-webpack-plugin`
     isn't used in development).
   
   For example, this reduces `time node .eslintrc.js` for a React+AirBnb
   project from 1700ms to 370ms - and for projects that use more of the
   non-default core Neutrino presets, the improvement will be even more
   noticeable.
   
   As an added bonus, plugins specified by path also have their `require()`
   statement generated automatically when using `toString()`, meaning
   that the configuration output by `--inspect` no longer needs any
   adjustments before it can be run.
   
   ie this "just works" with the core presets:
   
   ```
   $ echo "module.exports = $(yarn neutrino --inspect --mode production);" > exported-config.js
   $ yarn webpack --config exported-config.js
   ```
   
   The webpack-chain docs have also been synced with those from upstream.
   
   Refs #239.

   

   edmorley committed Sep 14, 2018
   Configuration menu

   • View commit details
   • Copy full SHA for 71ff0b2
   • Browse repository at this point

   Copy the full SHA

   71ff0b2 View commit details

   Browse the repository at this point in the history