stderr: [plugin:vite:reporter] [plugin vite:reporter] (!) /home/runner/work/_temp/waku-ssr-catch-error-iR5bYA/node_modules/waku/dist/middleware/context.js is dynamically imported by /home/runner/work/_temp/waku-ssr-catch-error-iR5bYA/node_modules/waku/dist/lib/config.js, /home/runner/work/_temp/waku-ssr-catch-error-iR5bYA/waku.config.ts but also statically imported by /home/runner/work/_temp/waku-ssr-catch-error-iR5bYA/node_modules/waku/dist/server.js, dynamic import will not move module into another chunk.

stderr: [plugin:vite:reporter] [plugin vite:reporter] (!) /home/runner/work/_temp/waku-ssr-catch-error-daqNPb/node_modules/waku/dist/middleware/context.js is dynamically imported by /home/runner/work/_temp/waku-ssr-catch-error-daqNPb/node_modules/waku/dist/lib/config.js, /home/runner/work/_temp/waku-ssr-catch-error-daqNPb/waku.config.ts but also statically imported by /home/runner/work/_temp/waku-ssr-catch-error-daqNPb/node_modules/waku/dist/server.js, dynamic import will not move module into another chunk.

stderr: [plugin:vite:reporter] [plugin vite:reporter] (!) /home/runner/work/_temp/waku-ssr-catch-error-ZjKFVH/node_modules/waku/dist/middleware/context.js is dynamically imported by /home/runner/work/_temp/waku-ssr-catch-error-ZjKFVH/node_modules/waku/dist/lib/config.js, /home/runner/work/_temp/waku-ssr-catch-error-ZjKFVH/waku.config.ts but also statically imported by /home/runner/work/_temp/waku-ssr-catch-error-ZjKFVH/node_modules/waku/dist/server.js, dynamic import will not move module into another chunk.

1) [webkit] › ssr-basic.spec.ts:51:5 › ssr-basic: dev › increase counter ───────────────────────── Error: Timed out 10000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('count') Expected string: "3" Received string: "2" Call log: - expect.toHaveText with timeout 10000ms - waiting for getByTestId('count') - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" - locator resolved to <p data-testid="count">2</p> - unexpected value "2" 56 | await page.getByTestId('increment').click(); 57 | await page.getByTestId('increment').click(); > 58 | await expect(page.getByTestId('count')).toHaveText('3'); | ^ 59 | }); 60 | 61 | test('vercel ai', async ({ page }) => { at /home/runner/work/waku/waku/e2e/ssr-basic.spec.ts:58:47

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

[webkit] › use-router.spec.ts took 1.7m

[webkit] › multi-platform.spec.ts took 57.7s

[webkit] › ssr-catch-error.spec.ts took 44.8s

[webkit] › ssg-performance.spec.ts took 26.1s

[webkit] › partial-builds.spec.ts took 24.0s

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "playwright-report-ubuntu-latest-18.17.0-4", "playwright-report-ubuntu-latest-20.8.0-4", "playwright-report-windows-latest-22.7.0-1", "playwright-report-windows-latest-22.7.0-2", "playwright-report-windows-latest-22.7.0-3", "playwright-report-windows-latest-22.7.0-4". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/