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 has been archived by the owner on Aug 11, 2021. It is now read-only.
It seems that the env.npm_execpath is set to require.main.filename "instead" of $execPath (used instead to set env.npm_node_execpath). I don't know if it's right or not and I'm not aware of all the possible side-effects of changing it.
The original problem comes from my nprr package that runs a package.json script through npm.run()(by importing npm itself). Here's the code that does that.
Hi
An issue found when working on my nprr package and npm-run-all makes me open this issue.
It seems that the
env.npm_execpath
is set torequire.main.filename
"instead" of$execPath
(used instead to setenv.npm_node_execpath
). I don't know if it's right or not and I'm not aware of all the possible side-effects of changing it.The original problem comes from my nprr package that runs a package.json script through
npm.run()
(by importing npm itself). Here's the code that does that.The "guilty" LOC of this project:
npm-lifecycle/index.js
Line 96 in e2270ff
Original issue: mysticatea/npm-run-all#181
I think that the correct label for this issue should be "support".
Thank you for all
Stefano
The text was updated successfully, but these errors were encountered: