-
Notifications
You must be signed in to change notification settings - Fork 667
CONSOLE-2758: Bump webpack-cli and webpack-dev-server to latest version #8269
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CONSOLE-2758: Bump webpack-cli and webpack-dev-server to latest version #8269
Conversation
d05a876 to
364a057
Compare
|
Right now, latest |
spadgett
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
Since this is a dev-only dependency, this does not need QE review. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
zherman0
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, will complete the other bump PRs once this merges
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spadgett, vojtechszocs, zherman0 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
10 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
Holding until #8289 merges to unblock CI. /hold |
|
/hold cancel |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
The webpack-cli upgrade in openshift/console#8269 was only made in 4.8. The analyze job will fail in 4.7 due to the older webpack-cli version, so we should remain on v21 for 4.7.
webpack-clibumped from3.3.9to4.5.0webpack-dev-serverbumped from3.11.0to3.11.1@types/webpack-dev-serverdev-dependencyThe
devscript has been updated to invokewebpack-dev-servervia webpack CLI.Starting with
webpack-cliv4, this is the standard way to run the dev-server. See here for details.The
analyzescript has been updated to match changes inwebpack-cliv4. See here for details.Our main
yarn.lockfile contains some resolutions pointing tohttps://registry.npmjs.org/instead of the expectedhttps://registry.yarnpkg.com/and found this Yarn issue which is fixed in Yarn v2 only.