Webpack Silent Shell Plugin
Forked from webpack-shell-plugin, is silent by default.
This plugin allows you to run any shell commands before or after webpack builds. This will work for both webpack and webpack-dev-server.
Goes great with running cron jobs, reporting tools, or tests such as selenium, protractor, phantom, ect.
WARNING
This plugin is meant for running simple command line executions. It is not meant to be a task management tool.
Installation
npm install --save-dev webpack-shell-runner
Setup
In webpack.config.js
:
const WebpackSilentShellPlugin = ; moduleexports = ... ... plugins: onBuildStart:'echo "Webpack Start"' onBuildEnd:'echo "Webpack End"' ...
Example
Insert into your webpack.config.js:
const WebpackSilentShellPlugin = ;const path = ; var plugins = ; plugins; var config = entry: app: path output: path: path // regular webpack filename: 'bundle.js' devServer: contentBase: path // dev server plugins: plugins module: loaders: test: /\.js$/ loaders: 'babel' test: /\.scss$/ loader: 'style!css!scss?' test: /\.html$/ loader: 'html-loader' moduleexports = config;
Once the build finishes, a child process is spawned firing both a python and node script.
API
onBuildStart
: array of scripts to execute on the initial build. Default: [ ]onBuildEnd
: array of scripts to execute after files are emitted at the end of the compilation. Default: [ ]onBuildExit
: array of scripts to execute after webpack's process is complete. Note: this event also fires inwebpack --watch
when webpack has finished updating the bundle. Default: [ ]dev
: switch for development environments. This causes scripts to execute once. Useful for running HMR on webpack-dev-server or webpack watch mode. Default: truesafe
: switches script execution process from spawn to exec. If running into problems with spawn, turn this setting on. Default: falseverbose
: enable for verbose output. Default: false
Developing
If opening a pull request, create an issue describing a fix or feature. Have your pull request point to the issue by writing your commits with the issue number in the message.
Make sure you lint your code by running npm run lint
and you can build the library by running npm run build
.
I appreciate any feed back as well, Thanks for helping!
Contributions
Yair Tavor Tom Lea