Globally catching all errors and outputting a string of text like Config file does not exist...
Using console.log to output this debug information prevents the script from exiting with a failing exit code instead it exits status 0, also it doesn't give useful information as to why the module was not found,
I think not catching the errors here would likely be a more useful output than a catch all that gives a very vague generic error message.
🐛 Bug Report
In cli.js there is a snippet of code like
Globally catching all errors and outputting a string of text like
Config file does not exist...Using console.log to output this debug information prevents the script from exiting with a failing exit code instead it exits status 0, also it doesn't give useful information as to why the module was not found,
I think not catching the errors here would likely be a more useful output than a catch all that gives a very vague generic error message.
To Reproduce
A minimal reproducible example. A codesandbox example or similar or at least steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Your Environment