Skip to content

Releases: modernweb-dev/web

@web/[email protected]

21 May 14:48
4ce4866
Compare
Choose a tag to compare

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]

19 May 15:19
c9ee4f8
Compare
Choose a tag to compare

Patch Changes

  • 1b53424: allow React 19 and test with it

@web/[email protected]

14 May 16:48
e47eb86
Compare
Choose a tag to compare

Patch Changes

  • 805e58c: fix Storybook 8 compatibility

@web/[email protected]

13 May 20:11
bcf30ab
Compare
Choose a tag to compare

Patch Changes

@web/[email protected]

13 May 20:11
bcf30ab
Compare
Choose a tag to compare

Patch Changes

  • 7e0af43: bump storybook packages to 8.6.12

@web/[email protected]

10 Apr 12:13
29f73c5
Compare
Choose a tag to compare

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]

10 Apr 12:13
29f73c5
Compare
Choose a tag to compare

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/[email protected]

02 Apr 17:42
31c3561
Compare
Choose a tag to compare

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)

@web/[email protected]

25 Mar 14:59
3cd0b1f
Compare
Choose a tag to compare

Patch Changes

  • b3f7313: dont path.join on external urls, it breaks them

@web/[email protected]

28 Feb 10:18
985cb56
Compare
Choose a tag to compare

Patch Changes

  • da68f94: publish as esm instead of commonjs