Closed xlch88 closed 1 year ago
two things:
Furthermore, I don't think that pkg needs to keep adding features and enhancements, since we can't even get our act together to make regular releases (this one's on me, I'll be the first to admit).
A reasonable workaround for someone who actually needs this is to patch their own version of pkg and use that to build their own binaries.
This pull-request is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this pull-request entirely you can add the no-stale label
This pull-request is now closed due to inactivity, you can of course reopen or reference this pull-request if you see fit.
Simply using
PKG_EXECPATH
to distinguish whether it is a child process is unreliable, which may cause many problems or side effects. For example, when usingchild_process.exec
to execute itself, the first parameter must be passed into the js file path. That is to say, when other programs that use pkg to package execute themselves, the first parameter must be passed in the js file path.The maintainer should consider refactoring this part or directly provide the native method of nodejs. In fact, the maintainer has "backed up" the native method of nodejs
Now just add
childProcess._ancestor = ancestor;
on it and everything should be fine.