chore(deps): update dependency webpack-cli to v5
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| webpack-cli (source) | 4.10.0 -> 5.1.4 |
Release Notes
webpack/webpack-cli (webpack-cli)
v5.1.4
Bug Fixes
- multi compiler progress output (f659624)
v5.1.3
Bug Fixes
v5.1.2
Bug Fixes
- improve check for custom webpack and webpack-dev-server package existance (0931ab6)
- improve help for some flags (f468614)
- improved support for
.ctsand.mtsextensions (a77daf2)
v5.1.1
Bug Fixes
v5.1.0
Features
Performance Improvements
5.0.2 (2023-04-21)
Bug Fixes
- error message for missing default export in configuration (#3685) (e0a4a09)
- perf: reduced startup time (3b79059)
5.0.1 (2022-12-05)
Bug Fixes
v5.0.2
Bug Fixes
- error message for missing default export in configuration (#3685) (e0a4a09)
- perf: reduced startup time (3b79059)
v5.0.1
Bug Fixes
v5.0.0
Bug Fixes
- improve description of the
--disable-interpretoption (#3364) (bdb7e20) - remove the redundant
utilsexport (#3343) (a9ce5d0) - respect
NODE_PATHenv 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-envoption - update
interpretto v3 andrechoirto 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
migratecommand (#3291) (56b43e4), closes #3291 - remove the
--prefetchoption in favor thePrefetchPluginplugin - remove the
--node-envoption in favor--define-process-env-node-env - remove the
--hotoption in favor of directly using theHotModuleReplacementplugin (only forbuildcommand, forserveit will work) - the behavior logic of the
--entryoption has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please usewebpack --entry-reset --entry './src/my-entry.js'
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @webpack-cli/[email protected]
npm warn Found: [email protected]
npm warn node_modules/webpack-cli
npm warn dev webpack-cli@"5.1.4" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/configtest
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/webpack-cli
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/configtest
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @webpack-cli/[email protected]
npm warn Found: [email protected]
npm warn node_modules/webpack-cli
npm warn dev webpack-cli@"5.1.4" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/info
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/webpack-cli
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/info
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @webpack-cli/[email protected]
npm error Found: [email protected]
npm error node_modules/webpack-cli
npm error dev webpack-cli@"5.1.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm error node_modules/@webpack-cli/serve
npm error dev @webpack-cli/serve@"1.7.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/webpack-cli
npm error peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm error node_modules/@webpack-cli/serve
npm error dev @webpack-cli/serve@"1.7.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-08T17_04_46_516Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-08T17_04_46_516Z-debug-0.log
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @webpack-cli/[email protected]
npm warn Found: [email protected]
npm warn node_modules/webpack-cli
npm warn dev webpack-cli@"5.1.4" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/configtest
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/webpack-cli
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/configtest
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @webpack-cli/[email protected]
npm warn Found: [email protected]
npm warn node_modules/webpack-cli
npm warn dev webpack-cli@"5.1.4" from the root project
npm warn
npm warn Could not resolve dependency:
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/info
npm warn
npm warn Conflicting peer dependency: [email protected]
npm warn node_modules/webpack-cli
npm warn peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm warn node_modules/@webpack-cli/info
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @webpack-cli/[email protected]
npm error Found: [email protected]
npm error node_modules/webpack-cli
npm error dev webpack-cli@"5.1.4" from the root project
npm error
npm error Could not resolve dependency:
npm error peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm error node_modules/@webpack-cli/serve
npm error dev @webpack-cli/serve@"1.7.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/webpack-cli
npm error peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm error node_modules/@webpack-cli/serve
npm error dev @webpack-cli/serve@"1.7.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-09-12T22_15_02_850Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-09-12T22_15_02_850Z-debug-0.log