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
{{ message }}
Repository navigation
deno: 22 of 24 orchestrion suites never load the real library #23897
In dev-packages/deno-integration-tests/suites/orchestrion-*, only orchestrion-mysql and orchestrion-postgres spawn a real deno run scenario. The other 22 publish the diagnostics channel by hand:
That tests the subscriber, which is shared with Node and already covered there. It proves nothing about whether Deno's Module.registerHooks transform actually injects the channel into that package. The Deno-specific risk is exactly the part not covered.
Work item. Promote three or four suites to real scenarios: express (the most-used), redis, and one AI provider. Reuse the scenario.mjs + Deno.Command shape from orchestrion-mysql.
**Prior art **(related history only). No issue. #21827 (merged) created the deno-integration-tests package that these suites live in. #18635 (open) is the nearest umbrella.
Activity
linear-code commentedon Sep 2, 2026
JS-3523
fix(server-runtime-injection): Keep ES modules working on Deno (#24669)
test(deno): Run all Node integration suites on Deno (#24611)
github-actions commentedon Sep 28, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #24611, which was included in the 11.1.0 release.