Describe the bug
Launched webpack-cli --info-verbosity verbose. Got an error/exit at:
/node_modules/webpack-cli/bin/webpack.js:460
compiler.hooks.beforeCompile.tap("WebpackInfo", compilation => {
due to the beforeCompile hook being undefined.
What is the current behavior?
Errors if --info-verbosity is used.
To Reproduce
- Launch webpack-cli with flag --info-verbosity verbose.
- See webpack exit with error at:
/node_modules/webpack-cli/bin/webpack.js:460
compiler.hooks.beforeCompile.tap("WebpackInfo", compilation => {
Expected behavior
Expect info-verbosity switch with verbose to cause webpack-cli to display messages before and after compilation that can be used with vscode problem matches to convert errors to "problems" in the UI.
Screenshots
*Please paste the results of webpack-cli info here, and mention other relevant information
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Binaries:
Node: 8.9.1
Yarn: 1.5.1
npm: 5.6.0
Browsers: {}
npmPackages:
case-sensitive-paths-webpack-plugin:
wanted: ^2.1.2
installed: 2.1.2
copy-webpack-plugin:
wanted: ^4.5.1
installed: 4.5.1
eslint-import-resolver-webpack:
wanted: ^0.10.0
installed: 0.10.0
extract-text-webpack-plugin:
wanted: ^4.0.0-beta.0
installed: 4.0.0-beta.0
fork-ts-checker-webpack-plugin:
wanted: ^0.4.1
installed: 0.4.1
only-if-changed-webpack-plugin:
wanted: 0.0.1
installed: 0.0.1
optimize-css-assets-webpack-plugin:
wanted: ^4.0.1
installed: 4.0.1
uglifyjs-webpack-plugin:
wanted: ^1.2.5
installed: 1.2.5
webpack:
wanted: ^4.8.3
installed: 4.8.3
webpack-bundle-analyzer:
wanted: ^2.13.0
installed: 2.13.0
webpack-cleanup-plugin:
wanted: github:domehead100/webpack-cleanup-plugin
installed: 0.5.2
webpack-cli:
wanted: ^2.1.3
installed: 2.1.3
webpack-dashboard:
wanted: ^1.1.1
installed: 1.1.1
webpack-manifest-plugin:
wanted: ^2.0.2
installed: 2.0.3
webpack-merge:
wanted: ^4.1.2
installed: 4.1.2
webpack-node-externals:
wanted: ^1.7.2
installed: 1.7.2
webpack-runner:
wanted: ^3.0.1
installed: 3.0.1
webpack-shell-plugin:
wanted: ^0.5.0
installed: 0.5.0
webpack-visualizer-plugin:
wanted: ^0.1.11
installed: 0.1.11
Additional context
Describe the bug
Launched webpack-cli --info-verbosity verbose. Got an error/exit at:
due to the beforeCompile hook being undefined.
What is the current behavior?
Errors if --info-verbosity is used.
To Reproduce
Expected behavior
Expect info-verbosity switch with verbose to cause webpack-cli to display messages before and after compilation that can be used with vscode problem matches to convert errors to "problems" in the UI.
Screenshots
*Please paste the results of
webpack-cli infohere, and mention other relevant informationSystem:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Binaries:
Node: 8.9.1
Yarn: 1.5.1
npm: 5.6.0
Browsers: {}
npmPackages:
case-sensitive-paths-webpack-plugin:
wanted: ^2.1.2
installed: 2.1.2
copy-webpack-plugin:
wanted: ^4.5.1
installed: 4.5.1
eslint-import-resolver-webpack:
wanted: ^0.10.0
installed: 0.10.0
extract-text-webpack-plugin:
wanted: ^4.0.0-beta.0
installed: 4.0.0-beta.0
fork-ts-checker-webpack-plugin:
wanted: ^0.4.1
installed: 0.4.1
only-if-changed-webpack-plugin:
wanted: 0.0.1
installed: 0.0.1
optimize-css-assets-webpack-plugin:
wanted: ^4.0.1
installed: 4.0.1
uglifyjs-webpack-plugin:
wanted: ^1.2.5
installed: 1.2.5
webpack:
wanted: ^4.8.3
installed: 4.8.3
webpack-bundle-analyzer:
wanted: ^2.13.0
installed: 2.13.0
webpack-cleanup-plugin:
wanted: github:domehead100/webpack-cleanup-plugin
installed: 0.5.2
webpack-cli:
wanted: ^2.1.3
installed: 2.1.3
webpack-dashboard:
wanted: ^1.1.1
installed: 1.1.1
webpack-manifest-plugin:
wanted: ^2.0.2
installed: 2.0.3
webpack-merge:
wanted: ^4.1.2
installed: 4.1.2
webpack-node-externals:
wanted: ^1.7.2
installed: 1.7.2
webpack-runner:
wanted: ^3.0.1
installed: 3.0.1
webpack-shell-plugin:
wanted: ^0.5.0
installed: 0.5.0
webpack-visualizer-plugin:
wanted: ^0.1.11
installed: 0.1.11
Additional context