ForbesLindesay/spawn-sync

Install with non-default npm

Closed this issue · 1 comments

Unfortunately, some build systems are less than awesome.

In such cases as the one I'm dealing with, the npm being used isn't the one found on the PATH, so this this line executes a different version of npm compared to the one that was originally run. For us, this creates some chaos.

Maybe there's a way of finding the full path of the npm that was originally executed, and running that instead?

The environment variable npm_execpath can probably be used for this.