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
node:child_process now ships a real streaming spawn() ChildProcess plus execFile/execFileSync (#1780 / PR pending). The two remaining lines of the test_parity_child_process gap test are the named exports:
Today a value-form reference to child_process.ChildProcess (i.e. read, not called) hits the #463 unimplemented-surface guard at compile time:
Error: `child_process.ChildProcess` is not implemented in Perry — see
`perry --print-api-manifest` ... (#463)
This blocks test_parity_child_process.ts from compiling at all, so the gap test can't be flipped even though the spawn/exec/execFile/sync surface it exercises now works.
What to do
Expose child_process.ChildProcess as a callable/constructor value that prints [Function: ChildProcess] (a named function value is enough for the typeof/inspect probes; a working new ChildProcess() is a larger follow-up).
child_process.Stream should resolve to undefined (Node does not export it).
Together with # this is what's left to flip the test_parity_child_process gap test green.
Done — shipped in PR #1861 (merged). child_process.ChildProcess now reads as [Function: ChildProcess] (registered in the api-manifest so the #463 value-read guard no longer fires at compile time, and as a callable native export at runtime), and child_process.Stream resolves to undefined (Node does not export it).
Verified on main: test_parity_child_process.ts is byte-identical to node --experimental-strip-types and has been removed from test-parity/known_failures.json. The relevant lines:
Activity
feat(child_process): streaming spawn() ChildProcess + execFile/execFi…
feat(child_process,util): ChildProcess/Stream exports (#1856) + promi…
proggeramlug commentedon May 27, 2026
Done — shipped in PR #1861 (merged).
child_process.ChildProcessnow reads as[Function: ChildProcess](registered in the api-manifest so the #463 value-read guard no longer fires at compile time, and as a callable native export at runtime), andchild_process.Streamresolves toundefined(Node does not export it).Verified on
main:test_parity_child_process.tsis byte-identical tonode --experimental-strip-typesand has been removed fromtest-parity/known_failures.json. The relevant lines: