Releases: modernweb-dev/web
@web/[email protected]
Patch Changes
- cfcea9d: fix Node 22.18
@web/[email protected]
Patch Changes
- dbd6f47: bump playwright
@web/[email protected]
Minor Changes
- 25bdafb: Change output to avoid import.meta.url in non-ESM builds
@web/[email protected]
Patch Changes
- 7aedbaa: Summary Reporter - re-enabled error reporting and made option to disable browser logs and error reporting in this reporter
@web/[email protected]
Patch Changes
- 1b53424: allow React 19 and test with it
@web/[email protected]
Patch Changes
- 805e58c: fix Storybook 8 compatibility
@web/[email protected]
Patch Changes
- 7e0af43: bump storybook packages to 8.6.12
- Updated dependencies [7e0af43]
- @web/[email protected]
 
@web/[email protected]
Patch Changes
- 7e0af43: bump storybook packages to 8.6.12
@web/[email protected]
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/[email protected]
 
@web/[email protected]
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 duringstopSessioncan 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