-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't pass execPath or execArgs when forking #22
Comments
ctrombley
added a commit
to ctrombley/respawn
that referenced
this issue
Dec 5, 2017
ctrombley
added a commit
to ctrombley/respawn
that referenced
this issue
Dec 5, 2017
ctrombley
added a commit
to ctrombley/respawn
that referenced
this issue
Dec 5, 2017
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This would be useful for scenarios where the child process needs to use a different runtime than the parent.
From the docs for
child_process.fork
:This can be accomplished easily by plumbing these two params through the passed
opts
. I'd like to submit a PR but first I'd like some input from the maintainers on the testing approach:os
and choose the correct one to point at withexecPath
, then verifyprocess.execPath
from the child process. This seems like overkill.fs.symlink(process.execPath, newPath)
, pointexecPath
to symlinked node, then verifyprocess.execPath
from the child process. The symlink would then be deleted on test completion.child_process
with mock-require, mockery, proxyquire, rewire, etc.The text was updated successfully, but these errors were encountered: