OCPBUGS-74424: migrate yarn 1 to npm

[upalatucci]

For konflux we are required to switch

I took the chance to make sure the start-console script support zsh and switched from ts-loader to esbuild-loader for faster loading time

Ref: https://github.com/kubevirt-ui/kubevirt-plugin/pull/2708/changes#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519

kubevirt-ui/kubevirt-plugin#3298

[openshift-ci-robot]

@upalatucci: This pull request references Jira Issue OCPBUGS-74424, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gouyang

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

For konflux we are required to switch

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@upalatucci: This pull request references Jira Issue OCPBUGS-74424, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gouyang

Details

In response to this:

For konflux we are required to switch

I took the chance to make sure the start-console script support zsh and switched from ts-loader to esbuild-loader for faster loading time

Ref: https://github.com/kubevirt-ui/kubevirt-plugin/pull/2708/changes#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519

kubevirt-ui/kubevirt-plugin#3298

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 openshift-eng/jira-lifecycle-plugin repository.

[galkremer1]

Do you think we need to utilize something similar to -network-timeout 600000?

RUN npm config set fetch-retries 5 && \
    npm config set fetch-retry-mintimeout 20000 && \
    npm config set fetch-retry-maxtimeout 120000 && \
    npm ci && \
    npm run build

[upalatucci]

This flag was added because of some issues during cross-platform builds (like S390x build into a AMD platform with buildx) but i'm not sure if we'll get the same issue with npm. We could skip this and then add it if we get same issues with npm. What do u think?

[galkremer1]

Sounds good.

[galkremer1]

/retest

[galkremer1]

/retest

[pcbailey]

/lgtm

[galkremer1]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: galkremer1, upalatucci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [upalatucci]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@upalatucci: 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-tests	c09a0ba	link	true	/test e2e-tests
ci/prow/images	c09a0ba	link	true	/test images

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.