Process completed with exit code 1.

@mendix/skiplink-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)

Process completed with exit code 1.

@mendix/accessibility-helper-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/accessibility-helper-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)

Process completed with exit code 1.

@mendix/badge-button-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/badge-button-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)

Process completed with exit code 1.

@mendix/datagrid-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)

datagrid-web filtering integration: Error: expect(page).toHaveScreenshot(expected) failed 101 pixels (ratio 0.01 of all image pixels) are different. Snapshot: datagridFilteringIntegration.png Call log: - Expect "toHaveScreenshot(datagridFilteringIntegration.png)" with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 101 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 101 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(page).toHaveScreenshot(expected) failed 101 pixels (ratio 0.01 of all image pixels) are different. Snapshot: datagridFilteringIntegration.png Call log: - Expect "toHaveScreenshot(datagridFilteringIntegration.png)" with timeout 5000ms - verifying given screenshot expectation - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - 101 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - taking page screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - captured a stable screenshot - 101 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-web/e2e/filtering/DataGridFilteringIntegration.spec.js:55:24

closes a page: Error: expect(locator).toBeVisible() failed Locator: locator('.mx-name-pageTitle1').nth(1) Expected: visible Timeout: 5000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 5000ms - waiting for locator('.mx-name-pageTitle1').nth(1) - Error: expect(locator).toBeVisible() failed Locator: locator('.mx-name-pageTitle1').nth(1) Expected: visible Timeout: 5000ms Error: element(s) not found Call log: - Expect "toBeVisible" with timeout 5000ms - waiting for locator('.mx-name-pageTitle1').nth(1) at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/badge-button-web/e2e/onClick.spec.js:62:70

updates target attributes using a NF: Test timeout of 30000ms exceeded. - Test timeout of 30000ms exceeded.

visual comparison: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.widget-skip-link').first() Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. Snapshot: skiplink-focused.png Call log: - Expect "toHaveScreenshot(skiplink-focused.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.widget-skip-link').first() Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. Snapshot: skiplink-focused.png Call log: - Expect "toHaveScreenshot(skiplink-focused.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.widget-skip-link').first() - locator resolved to <a href="#" class="widget-skip-link mx-name-skipLink1">Skip to main content</a> - taking element screenshot - disabled all CSS animations - waiting for fonts to load... - fonts loaded - attempting scroll into view action - waiting for element to be stable - captured a stable screenshot - Expected an image 185px by 40px, received 177px by 36px. 1940 pixels (ratio 0.27 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js:72:32

skip link becomes visible when focused via keyboard: Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, 0)" Received string: "none" - Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, 0)" Received string: "none" at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js:33:27

skip link is present in DOM but initially hidden: Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, -48)" Received string: "none" - Error: expect(received).toContain(expected) // indexOf Expected substring: "matrix(1, 0, 0, 1, 0, -48)" Received string: "none" at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/skiplink-web/e2e/SkipLink.spec.js:21:27

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: andstor/file-existence-action@076e0072799f4942c8bc574a82233e1e4d13e9d6, pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

Missing return type on function

`./SizeContainer` import should occur after import of `./CalendarLoader`

`./Toolbar` import should occur after import of `./CalendarLoader`

`react-big-calendar` import should occur after import of `moment`

`../utils/namespaces` import should occur after import of `./CalendarLoader`

`./Alert` import should occur after import of `react-big-calendar/lib/addons/dragAndDrop`

`react` import should occur after import of `moment`

`classnames` import should occur before import of `react`

`classnames` import should occur before import of `react`

`./utils/style` import should occur before import of `./utils/validation`

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

`react` import should occur before import of `../typings/TXhHdGFnProps`

`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`

`./utils` import should occur before import of `../typings/TXhHdGFnProps`

`@mendix/pluggable-widgets-tools` import should occur before import of `../typings/TXhHdGFnProps`

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@41ff72655975bd51cab0327fa583b6e92b6d3061. 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/

`react` import should occur before import of `../typings/TXhHdGFnProps`

`./commonGtag` import should occur before import of `../typings/TXhHdGFnProps`

`./utils` import should occur before import of `../typings/TXhHdGFnProps`