CLI does not respect shelljs errors
See original GitHub issueShelljs module does not fail in case shelljs.config.fatal
is not set to true. However setting it true leads to some unexpected issues - the shelljs silently exits the process when calling tns platform add android@1.3.0
for example.
So consider respecting the errors of shelljs, but make sure all operations work.
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
NodeJS: How to synchronously exewcute shell command and ...
The README of shell.js explains: Executes the given command synchronously, unless otherwise specified. When in synchronous mode, this returns a ...
Read more >shelljs | Yarn - Package Manager
ShellJS is a portable (Windows/Linux/OS X) implementation of Unix shell commands on top of the Node.js API. You can use it to eliminate...
Read more >gist-charts/node_modules/shelljs/CHANGELOG.md - GitLab
Snyk vulnerability DB reporting command injection vulnerability in ... ShellJS doesn't respect NPM Registry being set outside of it #761 ...
Read more >mesonet.org/scripts/okfire/node_modules/ocspackage...
[\#639](https://github.com/shelljs/shelljs/issues/639) - mkdir fails with ... parseOptions should throw an error if the option string doesn't start with ...
Read more >Working with JavaScript in Visual Studio Code
Configuration options from your jsconfig or tsconfig (such as target ) are not respected. Only syntax errors are reported. Semantic errors — such...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think we should increase the priority of this issue as I was debugging entirely different problem only to find that there were silent/missing error handling.
@Plamen5kov I think in most of the cases we would like to stop the execution in case shelljs encounters an error. However (as far as I remember), setting
shelljs.config.fatal
breaks the process immediately, so we have no chance to catch this. My suggestion is: