Package Exports
- npm-install-webpack-plugin
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (npm-install-webpack-plugin) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
npm-install-webpack-plugin
Speed up development by automatically installing & saving dependencies with Webpack.
Features
- Works with both Webpack
^v1.12.0and^2.1.0-beta.0. - Auto-installs
.babelrcplugins & presets. - Supports both ES5 & ES6 Modules.
(e.g.
require,import) - Supports Namespaced packages.
(e.g.
@cycle/dom) - Supports Dot-delimited packages.
(e.g.
lodash.capitalize) - Supports CSS imports.
(e.g.
@import "~bootstrap") - Supports Webpack loaders.
(e.g.
babel-loader,file-loader, etc.) - Supports inline Webpack loaders.
(e.g.
require("bundle?lazy!./App") - Auto-installs missing
peerDependencies. (e.g.@cycle/corewill automatically installrx@*) - Supports Webpack's
resolve.alias&resolve.rootconfiguration. (e.g.require("react")can alias toreact-lite)
Why?
It sucks to Ctrl-C your build script & server just to install a dependency you didn't know you needed until now.
Instead, use require or import how you normally would and npm install
will happen automatically to install & save missing dependencies while you work!
Installation
$ npm install --save-dev npm-install-webpack-pluginUsage
In your webpack.config.js:
plugins: [
new NpmInstallPlugin(),
],If you have an .npmrc file in your project,
those arguments will be used:
save=true
save-exact=trueAlternatively, you can provide your own arguments to npm install:
plugins: [
new NpmInstallPlugin({
...
cacheMin: 999999 // --cache-min=999999 (prefer NPM cached version)
registry: "..." // --registry="..."
save: true, // --save
saveDev: true, // --save-dev
saveExact: true, // --save-exact
...
}),
],License
MIT License 2016 © Eric Clemmons