You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test(deno): Run all Node integration suites on Deno
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.
Running these suites found that `@sentry/node` did not instrument ES
modules on Deno: Deno's module hooks report no `format` for an ES
module, so the orchestrion transform treated it as CommonJS and injected
a `require()` that throws when the module loads. The Deno load hook now
restores the format.
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>
0 commit comments