Closed stropitek closed 6 years ago
execa()
does not work with commands without specifying the full path
You have to use execa.shell()
Sorry for the bad diff... Prettier...
execa() does not work with commands without specifying the full path
That's not true. See how I used it here for example:
I assumed because I had an ENOENT error when trying it with npm
> execa('npm', ['--version']).then(console.log)
Promise {
<pending>,
domain:
Domain {
domain: null,
_events:
{ removeListener: [Function: updateExceptionCapture],
newListener: [Function: updateExceptionCapture],
error: [Function: debugDomainError] },
_eventsCount: 3,
_maxListeners: undefined,
members: [] } }
> { stdout: '6.4.0',
stderr: '',
code: 0,
failed: false,
killed: false,
signal: null,
cmd: 'npm --version',
timedOut: false }
There seems to be something wrong in your test. What was the command?
I published generator-cheminfo with those changes and it worked fine
Was able to see npm publish error, fix and then publish