chore: normalize package.json
#10572
nodejs.yml
on: pull_request
Matrix: Lint
Matrix: Smoketests
Matrix: test
Annotations
18 errors and 9 warnings
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L87
Package top-level property "peerDependencies" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L49
Package top-level property "devDependencies" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L25
Package top-level property "scripts" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L22
Package top-level property "workspaces" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L21
Package top-level property "license" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L17
Package top-level property "funding" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L13
Package top-level property "repository" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L5
Package top-level property "keywords" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L4
Package top-level property "description" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Lint (ubuntu-latest, lts/*, latest):
package.json#L3
Package top-level property "private" is not ordered in the npm standard way. Run the ESLint auto-fixer to correct
|
|
Test - windows-latest - Node v25.x, Webpack latest, DevServer latest
Canceling since a higher priority waiting request for test-windows-latest-v25.x-latest-latest-refs/pull/4700/merge exists
|
|
Test - windows-latest - Node v25.x, Webpack latest, DevServer latest
The operation was canceled.
|
|
Test - windows-latest - Node v20.x, Webpack latest, DevServer latest
Canceling since a higher priority waiting request for test-windows-latest-v20.x-latest-latest-refs/pull/4700/merge exists
|
|
Test - windows-latest - Node v20.x, Webpack latest, DevServer latest
The operation was canceled.
|
|
Test - windows-latest - Node v24.x, Webpack latest, DevServer latest
Canceling since a higher priority waiting request for test-windows-latest-v24.x-latest-latest-refs/pull/4700/merge exists
|
|
Test - windows-latest - Node v24.x, Webpack latest, DevServer latest
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest, DevServer latest
Canceling since a higher priority waiting request for test-windows-latest-v22.x-latest-latest-refs/pull/4700/merge exists
|
|
Test - windows-latest - Node v22.x, Webpack latest, DevServer latest
The operation was canceled.
|
|
Smoketests (ubuntu-latest, lts/*)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - macos-latest - Node v25.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - ubuntu-latest - Node v25.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - ubuntu-latest - Node v22.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - ubuntu-latest - Node v24.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - ubuntu-latest - Node v20.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - macos-latest - Node v22.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - macos-latest - Node v24.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Test - macos-latest - Node v20.x, Webpack latest, DevServer latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|