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 }}
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 24, 2026. It is now read-only.
Support for hooking spawn / spawnSync without patching. #48
By default nyc 15 will be using node-preload instead of spawn-wrap. v0.1.x was fine for nyc's specific use case but I do not believe it's generic enough to be part of node.js. In particular it did not support alteration of variables (prepending / appending an existing value) nor does it allow control over conditional variable propagation (setting a variable only if it doesn't already exist).
I've created process-on-spawn. I think this may be generic enough to serve any situation where the environment of child processes must be centrally manipulated/controlled. This new module does not have direct support for propagating variables to grand-child processes and it doesn't help with adding --require options to NODE_OPTIONS. I've altering node-preload to use process-on-spawn instead of directly patching spawn / spawnSync functions, so the two modules work together.
My hope is to work towards getting the functionality of process-on-spawn into node.js so nyc can eventually avoid patching spawn / spawnSync.
The plan is to continue the discussion in nodejs/diagnostics#401. I'll be getting back to working on this stuff full-time again in about a week. Until then, I'll be a bit less active for now. If you have any thoughts to share now though, I'm happy to discuss. :)
Activity
coreyfarrell commentedon Nov 15, 2019
wesleytodd commentedon Jul 24, 2020
@Qard Where is the best place for us to engage on the proposal for unified hooks and this feature?
Qard commentedon Jul 24, 2020
The plan is to continue the discussion in nodejs/diagnostics#401. I'll be getting back to working on this stuff full-time again in about a week. Until then, I'll be a bit less active for now. If you have any thoughts to share now though, I'm happy to discuss. :)