Output to a file

[stephencookdev]

This PR adds in the ability to output to a file, as well as just to the console. (should resolve #8)

For example, with a config of:

new UnusedWebpackPlugin({
  // Source directories
  directories: [
    path.join(__dirname, 'awesome-module'),
    path.join(__dirname, 'simple-module'),
  ],
  // Exclude patterns
  exclude: ['**/*.test.js'],
  // Root directory (optional)
  root: __dirname,
  failOnUnused: false,
})

you would get this logged to the console:

*** Unused Plugin ***
4 unused source files found.

● awesome-module
    • actions/destroy.js
    • config/index.js

● simple-module
    • routes/index.js
    • utils/date.js

*** Unused Plugin ***

but with the following config, instead:

new UnusedWebpackPlugin({
  // Source directories
  directories: [
    path.join(__dirname, 'awesome-module'),
    path.join(__dirname, 'simple-module'),
  ],
  // Exclude patterns
  exclude: ['**/*.test.js'],
  // Root directory (optional)
  root: __dirname,
  failOnUnused: false,
  outputFile: 'unused_manifest',
})

then you would get nothing printing to the console, but cat dist/unused_manifest would return:

/some/user/path/unused-webpack-plugin/examples/awesome-module/actions/destroy.js                                                                                        
/some/user/path/unused-webpack-plugin/examples/awesome-module/config/index.js
/some/user/path/unused-webpack-plugin/examples/simple-module/routes/index.js
/some/user/path/unused-webpack-plugin/examples/simple-module/utils/date.js

[stephencookdev]

D'oh, I've just noticed that #35 also does what I've done here 😂

I think strictly speaking compilation.assets is the preferred way to output new files in webpack, but I don't have a strong opinion, other than feature existing in some form 🙂