Process completed with exit code 1.

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

Process completed with exit code 1.

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

Process completed with exit code 1.

@mendix/line-chart-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/line-chart-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-dropdown-filter-web#e2e: command (/home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-dropdown-filter-web) /home/runner/setup-pnpm/node_modules/.bin/pnpm run e2e exited (1)

Process completed with exit code 1.

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

compares with a screenshot baseline and checks if all slider elements are rendered as expected: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-sliderPrimary') 15 pixels (ratio 0.01 of all image pixels) are different. Snapshot: sliderStyles.png Call log: - Expect "toHaveScreenshot(sliderStyles.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-sliderPrimary') - locator resolved to <div class="mx-name-sliderPrimary widget-slider-primary form-group no-columns">…</div> - 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 - 15 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-sliderPrimary') - locator resolved to <div class="mx-name-sliderPrimary widget-slider-primary form-group no-columns">…</div> - 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 - 15 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-sliderPrimary') 15 pixels (ratio 0.01 of all image pixels) are different. Snapshot: sliderStyles.png Call log: - Expect "toHaveScreenshot(sliderStyles.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-sliderPrimary') - locator resolved to <div class="mx-name-sliderPrimary widget-slider-primary form-group no-columns">…</div> - 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 - 15 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-sliderPrimary') - locator resolved to <div class="mx-name-sliderPrimary widget-slider-primary form-group no-columns">…</div> - 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 - 15 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/slider-web/e2e/Slider.spec.js:207:66

shows the expected result: Error: expect(locator).toHaveCount(expected) failed Locator: locator('.mx-name-datagrid1 .tr') Expected: 1 Received: 2 Timeout: 5000ms Call log: - Expect "toHaveCount" with timeout 5000ms - waiting for locator('.mx-name-datagrid1 .tr') 2 × locator resolved to 4 elements - unexpected value "4" 7 × locator resolved to 2 elements - unexpected value "2" - Error: expect(locator).toHaveCount(expected) failed Locator: locator('.mx-name-datagrid1 .tr') Expected: 1 Received: 2 Timeout: 5000ms Call log: - Expect "toHaveCount" with timeout 5000ms - waiting for locator('.mx-name-datagrid1 .tr') 2 × locator resolved to 4 elements - unexpected value "4" 7 × locator resolved to 2 elements - unexpected value "2" at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/datagrid-dropdown-filter-web/e2e/DataGridDropDownFilter.spec.js:26:66

compares with a screenshot baseline and checks if all badge buttons elements are rendered as expected: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-badgeButtonDynamic') 32 pixels (ratio 0.01 of all image pixels) are different. Snapshot: badgeButtonPageContent.png Call log: - Expect "toHaveScreenshot(badgeButtonPageContent.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-badgeButtonDynamic') - locator resolved to <button class="widget-badge-button btn mx-name-badgeButtonDynamic btn-warning">…</button> - 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 - 32 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-badgeButtonDynamic') - locator resolved to <button class="widget-badge-button btn mx-name-badgeButtonDynamic btn-warning">…</button> - 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 - 32 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-badgeButtonDynamic') 32 pixels (ratio 0.01 of all image pixels) are different. Snapshot: badgeButtonPageContent.png Call log: - Expect "toHaveScreenshot(badgeButtonPageContent.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-badgeButtonDynamic') - locator resolved to <button class="widget-badge-button btn mx-name-badgeButtonDynamic btn-warning">…</button> - 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 - 32 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-badgeButtonDynamic') - locator resolved to <button class="widget-badge-button btn mx-name-badgeButtonDynamic btn-warning">…</button> - 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 - 32 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/badge-button-web/e2e/render.spec.js:31:67

verifies if tooltip is opened on click: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-scrollcontainer-center') 91 pixels (ratio 0.01 of all image pixels) are different. Snapshot: tooltipClick.png Call log: - Expect "toHaveScreenshot(tooltipClick.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-scrollcontainer-center') - locator resolved to <div class="mx-scrollcontainer-center region-content">…</div> - 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 - 91 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-scrollcontainer-center') - locator resolved to <div class="mx-scrollcontainer-center region-content">…</div> - 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 - 91 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-scrollcontainer-center') 91 pixels (ratio 0.01 of all image pixels) are different. Snapshot: tooltipClick.png Call log: - Expect "toHaveScreenshot(tooltipClick.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-scrollcontainer-center') - locator resolved to <div class="mx-scrollcontainer-center region-content">…</div> - 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 - 91 pixels (ratio 0.01 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-scrollcontainer-center') - locator resolved to <div class="mx-scrollcontainer-center region-content">…</div> - 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 - 91 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/tooltip-web/e2e/Tooltip.spec.js:88:70

renders heatmap chart with descending order and compares with a screenshot baseline: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerDescending') 32675 pixels (ratio 0.13 of all image pixels) are different. Snapshot: heatmapChartDescending.png Call log: - Expect "toHaveScreenshot(heatmapChartDescending.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerDescending') - locator resolved to <div class="mx-name-containerDescending">…</div> - 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 - 32675 pixels (ratio 0.13 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerDescending') - locator resolved to <div class="mx-name-containerDescending">…</div> - 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 - 32675 pixels (ratio 0.13 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerDescending') 32675 pixels (ratio 0.13 of all image pixels) are different. Snapshot: heatmapChartDescending.png Call log: - Expect "toHaveScreenshot(heatmapChartDescending.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerDescending') - locator resolved to <div class="mx-name-containerDescending">…</div> - 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 - 32675 pixels (ratio 0.13 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerDescending') - locator resolved to <div class="mx-name-containerDescending">…</div> - 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 - 32675 pixels (ratio 0.13 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/heatmap-chart-web/e2e/HeatMapChart.spec.js:39:47

renders heatmap chart with ascending order and compares with a screenshot baseline: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerAscending') 31941 pixels (ratio 0.13 of all image pixels) are different. Snapshot: heatmapChartAscending.png Call log: - Expect "toHaveScreenshot(heatmapChartAscending.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerAscending') - locator resolved to <div class="mx-name-containerAscending">…</div> - 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 - 31941 pixels (ratio 0.13 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerAscending') - locator resolved to <div class="mx-name-containerAscending">…</div> - 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 - 31941 pixels (ratio 0.13 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerAscending') 31941 pixels (ratio 0.13 of all image pixels) are different. Snapshot: heatmapChartAscending.png Call log: - Expect "toHaveScreenshot(heatmapChartAscending.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerAscending') - locator resolved to <div class="mx-name-containerAscending">…</div> - 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 - 31941 pixels (ratio 0.13 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerAscending') - locator resolved to <div class="mx-name-containerAscending">…</div> - 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 - 31941 pixels (ratio 0.13 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/heatmap-chart-web/e2e/HeatMapChart.spec.js:28:46

renders without legend and compares with a screenshot baseline: Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerNoLegend') 249 pixels (ratio 0.01 of all image pixels) are different. Snapshot: lineChartNoLegend.png Call log: - Expect "toHaveScreenshot(lineChartNoLegend.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerNoLegend') - locator resolved to <div class="mx-name-containerNoLegend">…</div> - 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 - 28601 pixels (ratio 0.12 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerNoLegend') - locator resolved to <div class="mx-name-containerNoLegend">…</div> - 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 - 28765 pixels (ratio 0.12 of all image pixels) are different. - waiting 250ms before taking screenshot - waiting for locator('.mx-name-containerNoLegend') - locator resolved to <div class="mx-name-containerNoLegend">…</div> - 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 - 249 pixels (ratio 0.01 of all image pixels) are different. - Error: expect(locator).toHaveScreenshot(expected) failed Locator: locator('.mx-name-containerNoLegend') 249 pixels (ratio 0.01 of all image pixels) are different. Snapshot: lineChartNoLegend.png Call log: - Expect "toHaveScreenshot(lineChartNoLegend.png)" with timeout 5000ms - verifying given screenshot expectation - waiting for locator('.mx-name-containerNoLegend') - locator resolved to <div class="mx-name-containerNoLegend">…</div> - 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 - 28601 pixels (ratio 0.12 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('.mx-name-containerNoLegend') - locator resolved to <div class="mx-name-containerNoLegend">…</div> - 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 - 28765 pixels (ratio 0.12 of all image pixels) are different. - waiting 250ms before taking screenshot - waiting for locator('.mx-name-containerNoLegend') - locator resolved to <div class="mx-name-containerNoLegend">…</div> - 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 - 249 pixels (ratio 0.01 of all image pixels) are different. at /home/runner/work/web-widgets/web-widgets/packages/pluggableWidgets/line-chart-web/e2e/LineChart.spec.js:92:43

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`

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