console
console copied to clipboard
[WIP] CONSOLE-2971: Update to webpack 5.28+
Fixes: https://issues.redhat.com/browse/CONSOLE-2971
Updated webpack and other requirements to 5.28+
[WIP] I have an issue with the addFilesToCompilation and addErrorsToCompilation functions as webpack variable no longer has a compilation member: TS2694: Namespace 'exports' has no exported member 'compilation'. @vojtechszocs @spadgett
Updated react-dnd as well to version 11.0, which is not the latest. I had to upgrade to 11 to work with webpack 5+, but I could not update to the latest version 14 because too much of the logic has changed and drag and drop of files breaks.
/cc @vojtechszocs
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/remove-lifecycle stale
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: zherman0
Once this PR has been reviewed and has the lgtm label, please assign jerolimov for approval by writing /assign @jerolimov in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@zherman0: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-gcp | c7af9068f9b31420859461930cd669c97d435c8e | link | true | /test e2e-gcp |
| ci/prow/e2e-gcp-console | 0f0adda6997deb93314b1e2968a1f82c1def9a70 | link | true | /test e2e-gcp-console |
| ci/prow/backend | 0f0adda6997deb93314b1e2968a1f82c1def9a70 | link | true | /test backend |
| ci/prow/analyze | 0f0adda6997deb93314b1e2968a1f82c1def9a70 | link | true | /test analyze |
| ci/prow/frontend | 0f0adda6997deb93314b1e2968a1f82c1def9a70 | link | true | /test frontend |
| ci/prow/kubevirt-plugin | 0f0adda6997deb93314b1e2968a1f82c1def9a70 | link | true | /test kubevirt-plugin |
| ci/prow/images | 0f0adda6997deb93314b1e2968a1f82c1def9a70 | link | true | /test images |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
@zherman0: PR needs rebase.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale