It seems that sb-exec is reporting that cc-cli is exiting with non-zero code. That is populating my Atom console with lots of console.error(...) messages, printing there all the data that the cli outputs.
When I exec the cli locally, I get an exit code $? of 0, so don't know why this is happening, but it's very annoying. As a temporary workaround, I can pass option ignoreExitCode: truehere, and now the package works flawlessly.
@Arcanemagus Let me know if you want me to make a PR with the temporary workaround :wink:
Just checked that exitCode === null when reaching this line, but the captured output is fine, and the spawned process exit flawlessly. Seems to be a bug of sb-exec.
cgalvarez
commented
6 years ago
It seems that
sb-execis reporting that cc-cli is exiting with non-zero code. That is populating my Atom console with lots ofconsole.error(...)messages, printing there all the data that the cli outputs.When I exec the cli locally, I get an exit code
$?of 0, so don't know why this is happening, but it's very annoying. As a temporary workaround, I can pass optionignoreExitCode: truehere, and now the package works flawlessly.@Arcanemagus Let me know if you want me to make a PR with the temporary workaround :wink: