Skip to content

feat: support webpack processContent hook for CSS embedded in JS #721

feat: support webpack processContent hook for CSS embedded in JS

feat: support webpack processContent hook for CSS embedded in JS #721

Triggered via pull request March 31, 2026 16:31
Status Cancelled
Total duration 42s
Artifacts

nodejs.yml

on: pull_request
Matrix: lint
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

22 errors and 8 warnings
Test - macos-latest - Node v20.x, Webpack latest
Canceling since a higher priority waiting request for test-macos-latest-v20.x-latest-refs/pull/311/merge exists
Test - macos-latest - Node v25.x, Webpack latest
Canceling since a higher priority waiting request for test-macos-latest-v25.x-latest-refs/pull/311/merge exists
Test - macos-latest - Node v24.x, Webpack latest
Canceling since a higher priority waiting request for test-macos-latest-v24.x-latest-refs/pull/311/merge exists
Test - macos-latest - Node v22.x, Webpack latest
Canceling since a higher priority waiting request for test-macos-latest-v22.x-latest-refs/pull/311/merge exists
Test - windows-latest - Node v25.x, Webpack latest
Canceling since a higher priority waiting request for test-windows-latest-v25.x-latest-refs/pull/311/merge exists
Test - windows-latest - Node v25.x, Webpack latest
The operation was canceled.
Test - ubuntu-latest - Node v20.x, Webpack latest
Canceling since a higher priority waiting request for test-ubuntu-latest-v20.x-latest-refs/pull/311/merge exists
Test - ubuntu-latest - Node v20.x, Webpack latest
The operation was canceled.
Test - windows-latest - Node v24.x, Webpack latest
Canceling since a higher priority waiting request for test-windows-latest-v24.x-latest-refs/pull/311/merge exists
Test - windows-latest - Node v24.x, Webpack latest
The operation was canceled.
Test - ubuntu-latest - Node v25.x, Webpack latest
Canceling since a higher priority waiting request for test-ubuntu-latest-v25.x-latest-refs/pull/311/merge exists
Test - ubuntu-latest - Node v25.x, Webpack latest
The operation was canceled.
Test - windows-latest - Node v22.x, Webpack latest
Canceling since a higher priority waiting request for test-windows-latest-v22.x-latest-refs/pull/311/merge exists
Test - windows-latest - Node v22.x, Webpack latest
The operation was canceled.
Test - windows-latest - Node v20.x, Webpack latest
Canceling since a higher priority waiting request for test-windows-latest-v20.x-latest-refs/pull/311/merge exists
Test - windows-latest - Node v20.x, Webpack latest
The operation was canceled.
Test - ubuntu-latest - Node v22.x, Webpack latest
Canceling since a higher priority waiting request for test-ubuntu-latest-v22.x-latest-refs/pull/311/merge exists
Test - ubuntu-latest - Node v22.x, Webpack latest
The operation was canceled.
Lint - ubuntu-latest - Node vlts/*
Canceling since a higher priority waiting request for lint-ubuntu-latest-vlts/*-refs/pull/311/merge exists
Lint - ubuntu-latest - Node vlts/*
The operation was canceled.
Test - ubuntu-latest - Node v24.x, Webpack latest
Canceling since a higher priority waiting request for test-ubuntu-latest-v24.x-latest-refs/pull/311/merge exists
Test - ubuntu-latest - Node v24.x, Webpack latest
The operation was canceled.
Test - ubuntu-latest - Node v20.x, Webpack latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 - windows-latest - Node v24.x, Webpack latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 - windows-latest - Node v22.x, Webpack latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 - windows-latest - Node v20.x, Webpack latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Lint - ubuntu-latest - Node vlts/*
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/