Bump webpack-cli from 4.1.0 to 4.5.0

[dependabot-preview]

Bumps webpack-cli from 4.1.0 to 4.5.0.

Release notes

Sourced from webpack-cli's releases.

v4.5.0

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

• add the --node-env flag (#2388) (e5126f1)
• entries syntax (#2369) (6b31614)
• support ES module configuration format (#2381) (aebdbbc)

v4.4.0

4.4.0 (2021-01-19)

Bug Fixes

• better description for --no-watch-options-stdin (#2288) (4ee8665)
• double commands output in help (#2298) (efe81e9)
• pass all argv to configurations when serve command used (#2345) (5070b9b)

... (truncated)

Changelog

Sourced from webpack-cli's changelog.

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

• add the --node-env flag (#2388) (e5126f1)
• entries syntax (#2369) (6b31614)
• support ES module configuration format (#2381) (aebdbbc)

4.4.0 (2021-01-19)

Bug Fixes

• better description for --no-watch-options-stdin (#2288) (4ee8665)
• double commands output in help (#2298) (efe81e9)
• pass all argv to configurations when serve command used (#2345) (5070b9b)
• respect --stats, --color and --no-color option for serve command (#2312) (73d3fec)
• show exact package name while prompting for installation (#2338) (ffc93e5)

... (truncated)

Commits

• 3bbda71 chore(release): publish new version
• e5126f1 feat: add the --node-env flag (#2388)
• 2841cd7 test: default loader name and plugin name (#2392)
• b50d71b test: improve tests for --merge (#2399)
• ad1a6b8 docs: update (#2398)
• 805f9ff chore: use conventional commitlint (#2394)
• 9967de9 chore(deps): bump envinfo from 7.7.3 to 7.7.4 (#2396)
• aebdbbc feat: support ES module configuration format (#2381)
• d004ded docs: remove references to non-existent packages (#2395)
• 7bd747a chore(init): remove --force flag (#2391)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

• node12.x

Dependabot will still automatically merge this pull request if you amend it and your tests pass.