Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

webpack-cleanup-plugin

gpbl17.2kMIT0.5.1TypeScript support: definitely-typed

Plugin for webpack to cleanup extraneous files from the output path directory

webpack, webpack-plugin

readme

webpack-cleanup-plugin

This webpack plugin cleans up the extraneous files from the webpack's output path.

Since it runs when the compile process is finished, it is useful when building on production to remove the assets created by previous builds.

npm install webpack-cleanup-plugin --save-dev

npm version npm downloads Build Status

⚠️ Beware! This plugins actually delete files. Make sure it's safe for your app to delete files not generated by webpack. Use the exclude option if you want to keep files that are not webpack assets.

Usage

Install via npm:

npm install webpack-cleanup-plugin --save-dev

Then add the plugin to the plugins array in your webpack's config, e.g.:

// webpack.config.js
import WebpackCleanupPlugin from 'webpack-cleanup-plugin';
const config = {
  output: {
    path: "/my/output/path"
  },
  // ...
  plugins: [
    new WebpackCleanupPlugin()
  ]
}
export default config;

Options

  • If you want to keep some files in the output path, e.g. a stats.json file generated from some other plugins, use the exclude Array option. It accepts globbing as in minimatch.
// Do not delete `stats.json`, `important.json`, and everything in `folder`
new WebpackCleanupPlugin({
  exclude: ["stats.json", "important.js", "folder/**/*"],
})
  • To mute the console output, use the quiet option:
new WebpackCleanupPlugin({
  quiet: true,
})
  • To print the list of the files that will be deleted without actually deleting them, use the preview option:
new WebpackCleanupPlugin({
  preview: true,
})

changelog

Changelog

v0.5.1 (2017-02-27)

v0.4.2 (2017-02-10)

v0.4.1 (2016-10-13)

v0.4.0 (2016-09-18)

  • Added preview option
  • Add support for minimatch globs to exclude option (#18 by geekuillaume).

v0.3.1 (2016-08-31)

  • Fixed an issue with plugin initialization (#14 by ifamed).

v0.3.0 (2016-08-20)

v0.2.0 (2016-02-13)

  • Error when initializing the plugin without options (#1, #6)
  • Directories were no cleaned up recursively (#2, #5)