Releases: webpack/webpack-cli
Releases · webpack/webpack-cli
v4.10.0
13 Jun 00:37
Compare
Sorry, something went wrong.
No results found
4.10.0 (2022-06-13)
Bug Fixes
Features
v4.9.2
24 Jan 13:24
Compare
Sorry, something went wrong.
No results found
4.9.2 (2022-01-24)
Bug Fixes
respect negatedDescription for flags from schema (#3102 ) (463b731 )
v4.9.1
18 Oct 11:20
Compare
Sorry, something went wrong.
No results found
4.9.1 (2021-10-18)
Bug Fixes
v4.9.0
06 Oct 20:39
Compare
Sorry, something went wrong.
No results found
4.9.0 (2021-10-06)
Bug Fixes
handle undefined and empty configuration export (#2930 ) (9b9040e )
Features
allow to run commands without webpack installation where it is unnecessary (#2907 ) (603041d )
v4.8.0
15 Aug 20:06
Compare
Sorry, something went wrong.
No results found
4.8.0 (2021-08-15)
Bug Fixes
Features
show possible values for option in help output (#2819 ) (828e5c9 )
init-generator: add ability to specify a package manager of choice (#2769 ) (e53f164 )
v4.7.2
07 Jun 16:39
Compare
Sorry, something went wrong.
No results found
4.7.2 (2021-06-07)
Note: Version bump only for package webpack-cli
v4.7.1
07 Jun 13:08
Compare
Sorry, something went wrong.
No results found
4.7.1 (2021-06-07)
Bug Fixes
v4.7.0
06 May 13:10
Compare
Sorry, something went wrong.
No results found
4.7.0 (2021-05-06)
Bug Fixes
Features
v4.6.0
27 Mar 15:37
Compare
Sorry, something went wrong.
No results found
4.6.0 (2021-03-27)
Bug Fixes
Features
added WEBPACK_PACKAGE env var to use custom webpack package (#2556 ) (3d1e485 )
added WEBPACK_CLI_SKIP_IMPORT_LOCAL env var to skip local import (#2546 ) (e130822 )
allow string value for the --hot option (#2444 ) (8656e78 )
display used config path when logging level=log (#2431 ) (f8406e1 )
v4.5.0
02 Feb 17:23
Compare
Sorry, something went wrong.
No results found
4.5.0 (2021-02-02)
Notes
now you can use webpack.config.mjs and webpack.config.js with { "type": "module" } in package.json
you can avoid using the cross-env package:
Before:
{
"scripts" : {
"build" : " cross-env NODE_ENV=production webpack --config build/webpack.config.js"
}
}
Now (you can remove the cross-env if you don't use it somewhere else):
{
"scripts" : {
"build" : " webpack --node-env=production --config build/webpack.config.js"
}
}
the mode option respect the --node-env option if you don't set the mode option explicit using CLI options or in configuration(s), i.e. --node-env production set process.env.NODE_ENV and mode to production
Bug Fixes
avoid deprecation message (9d6dbda )
error message on invalid plugin options (#2380 ) (f9ce1d3 )
improve description for 'configtest' command (#2379 ) (311bae3 )
Features