@web/test-runner-playwright@0.11.1

Patch Changes

• dbd6f47: bump playwright

@web/rollup-plugin-import-meta-assets@2.3.0

Minor Changes

• 25bdafb: Change output to avoid import.meta.url in non-ESM builds

@web/test-runner@0.20.2

Patch Changes

• 7aedbaa: Summary Reporter - re-enabled error reporting and made option to disable browser logs and error reporting in this reporter

@web/storybook-utils@1.1.2

Patch Changes

• 1b53424: allow React 19 and test with it

@web/mocks@1.3.2

Patch Changes

• 805e58c: fix Storybook 8 compatibility

@web/storybook-framework-web-components@0.2.1

Patch Changes

• 7e0af43: bump storybook packages to 8.6.12
• Updated dependencies [7e0af43]
  • @web/storybook-builder@0.2.2

@web/storybook-builder@0.2.2

Patch Changes

• 7e0af43: bump storybook packages to 8.6.12

@web/test-runner@0.20.1

Patch Changes

• 24e3290: Improve debug message for test runner uncaught exceptions

  This should make debugging easier. It wasn't very easy to figure out
  where the errors originated from (because of how the actual uncaught
  exception only happened with many concurrent builds inside a sandbox
  environment that is hard to debug).

• Updated dependencies [79b0ba4]

  • @web/test-runner-chrome@0.18.1

@web/test-runner-chrome@0.18.1

Patch Changes

• 79b0ba4: This changeset removes the Puppeteer/Chrome focus browser patches that shouldn't
  be needed anymore, and can cause instability.

  The patches were added quite a while ago, and the upstream issues should
  be resolved in Chromium. See: https://issues.chromium.org/issues/40272146.

  Also see:
  puppeteer/puppeteer#10350 (comment).

  The patches are currently also resulting some instability of web test
  runner. That is because the patch calls an exposed function from inside
  the browser, while navigation later on during stopSession can happen;
  breaking the handle for retrieving function call arguments passed to the
  exposed function.

  Puppeteer team found this issue and also landed a fix to improve the
  failure mode here. See:
  puppeteer/puppeteer#13759

@web/config-loader@0.3.3

Patch Changes

• d432f57: Optimizes config loading to not look for package.json in file system if the
  config extension is already informing whether CommonJS or ESM is used.

  Currently config loading did unnecessarily traverse the file system. This could
  be unnecessary slowness, or cause issues in sandbox environments (like Bazel)