build(deps-dev): bump webpack-cli from 4.10.0 to 5.0.0

[dependabot]

Bumps webpack-cli from 4.10.0 to 5.0.0.

Release notes

Sourced from webpack-cli's releases.

v5.0.0

5.0.0 (2022-11-17)

Bug Fixes

• improve description of the --disable-interpret option (#3364) (bdb7e20)
• remove the redundant utils export (#3343) (a9ce5d0)
• respect NODE_PATH env variable (#3411) (83d1f58)
• show all CLI specific flags in the minimum help output (#3354) (35843e8)

Features

• failOnWarnings option (#3317) (c48c848)
• update commander to v9 (#3460) (6621c02)
• added the --define-process-env-node-env option
• update interpret to v3 and rechoir to v0.8
• add an option for preventing interpret (#3329) (c737383)

BREAKING CHANGES

• the minimum supported webpack version is v5.0.0 (#3342) (b1af0dc), closes #3342
• webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
• webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
• remove the migrate command (#3291) (56b43e4), closes #3291
• remove the --prefetch option in favor the PrefetchPlugin plugin
• remove the --node-env option in favor --define-process-env-node-env
• remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
• the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

Changelog

Sourced from webpack-cli's changelog.

5.0.0 (2022-11-17)

Bug Fixes

• improve description of the --disable-interpret option (#3364) (bdb7e20)
• remove the redundant utils export (#3343) (a9ce5d0)
• respect NODE_PATH env variable (#3411) (83d1f58)
• show all CLI specific flags in the minimum help output (#3354) (35843e8)

Features

• failOnWarnings option (#3317) (c48c848)
• update commander to v9 (#3460) (6621c02)
• added the --define-process-env-node-env option
• update interpret to v3 and rechoir to v0.8
• add an option for preventing interpret (#3329) (c737383)

BREAKING CHANGES

• the minimum supported webpack version is v5.0.0 (#3342) (b1af0dc), closes #3342
• webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
• webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
• remove the migrate command (#3291) (56b43e4), closes #3291
• remove the --prefetch option in favor the PrefetchPlugin plugin
• remove the --node-env option in favor --define-process-env-node-env
• remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
• the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

Commits

• 1d6ada1 chore(release): 5.0.0 (#3492)
• 24334d9 refactor: resolve TODO for devServer.stdin
• 49b6aea chore: peer deps in root package
• 636ba3e chore(deps-dev): bump cspell from 6.12.0 to 6.14.2 (#3488)
• f3016a5 chore(deps-dev): bump eslint from 8.24.0 to 8.27.0 (#3487)
• 5782242 chore(deps-dev): bump lerna from 6.0.1 to 6.0.3 (#3486)
• 80eb8c8 chore(deps-dev): bump @​commitlint/config-conventional (#3485)
• 8ea9020 chore(deps-dev): bump ts-jest from 29.0.1 to 29.0.3 (#3484)
• 515971a chore(deps-dev): bump css-loader from 6.7.1 to 6.7.2 (#3481)
• f106109 chore(deps-dev): bump @​typescript-eslint/eslint-plugin
• 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.

---

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)

[andrewazores]

@dependabot rebase

[andrewazores]

@maxcao13 GitHub is really frustrating me here. I don't understand why, but the CI runner still sees the needs-triage label and fails the run even after I have manually removed the label and re-run the CI.

Maybe the CI check should be done as a separate workflow, not as a step within the CI / build workflow, and triggered on when the PR labels change? I'd hope that doing it that way, the CI runner properly sees the current state of the labels each time it runs.