Open tonioriol opened 4 years ago
This only happens when running the command through npm run
, presumably because when we run the cmp
command without any subcommands yargs sets the exit status to 1 and when npm run
gets that it prints this ugly error.
If we run it through node_modules/.bin/cmp
this doesnt happen.
Can't find a way to solve that so moving on.
Maybe has something to do with the use of
process.exitCode = 1
. Maybe only doprocess.exitCode = 1
when an unexpected error happens.