Conversation
Contributor
size-limit report 📦
|
JPeer264
added this pull request to stack #24613
September 23, 2026 06:14
JPeer264
force-pushed
the
jp/node-suites-deno
branch
from
September 23, 2026 07:29
38156ea to
ec8a598
Compare
JPeer264
force-pushed
the
jp/node-suites-deno
branch
2 times, most recently
from
September 23, 2026 08:27
a873afb to
e62dd7f
Compare
JPeer264
removed this pull request from stack #24613
September 23, 2026 09:51
JPeer264
added this pull request to stack #24633
September 23, 2026 09:51
JPeer264
force-pushed
the
jp/node-suites-deno
branch
2 times, most recently
from
September 23, 2026 10:04
8a5e324 to
77995a1
Compare
JPeer264
force-pushed
the
jp/node-suites-deno
branch
from
September 23, 2026 12:24
b8eb1d5 to
8931b15
Compare
JPeer264
force-pushed
the
jp/node-suites-deno
branch
from
September 23, 2026 13:23
8931b15 to
c75645c
Compare
JPeer264
force-pushed
the
jp/node-suites-deno
branch
2 times, most recently
from
September 23, 2026 16:19
17fdfc4 to
e4e9494
Compare
JPeer264
removed this pull request from stack #24633
September 23, 2026 16:19
JPeer264
changed the base branch from
jp/node-suites-bun
to
jp/node-suites-deno-esm-fix
September 23, 2026 16:19
JPeer264
added this pull request to stack #24670
September 23, 2026 16:19
The Deno package now selects every Node suite and excludes the ones that do not run on Deno, grouped by cause: Node-only features, no `fetch` instrumentation because Deno's `fetch` does not publish undici channels, a Prisma interop limit, suites that fail for a cause not investigated yet, and one flaky suite. The list is based on Deno 2.8.3, the version CI pins. The database suites run too, so the Deno CI job gets the disk space step and the 20 minute timeout of the Node integration job. The runner now starts every scenario in the `node-integration-tests` folder, because the Deno and Bun packages run the suites from their own folder and scenarios such as `modules` read the working directory. When a test times out, it prints the child output with the child state. `yarn test <filter>` now filters the shared suites, as in the other packages. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/node-suites-deno
branch
from
September 23, 2026 16:40
e4e9494 to
63b32cb
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
removed this pull request from stack #24670
September 23, 2026 17:26
JPeer264
added this pull request to stack #24671
September 23, 2026 17:31
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deno now runs every Node suite except an explicit exclude list, including the database suites that need Docker, so the Deno CI job gets the disk space step and timeout of the Node integration job. Unlike the Deno-only orchestrion suites, which mostly publish fake channel messages, these load the real libraries (#23897). They depend on the ES module fix in the previous PR of the stack.
Harness changes: scenarios always start in the
node-integration-testsfolder (some read the working directory), a test that times out prints the child's output and state, andyarn test <filter>works in this package as in the others.Closes #23897. Part of #24052.
🤖 Generated with Claude Code