Nate Fischer
Nate Fischer
Node docs suggest the API still exists, not sure you would get this error: https://nodejs.org/api/fs.html#fs_fs_existssync_path > shell.config.execPath = 'v14.1.0'; This isn't the right way to configure this. This needs to...
Did you grant `simple-script.sh` executable permission? ```sh chmod +x simple-script.sh ``` Or, your shelljs script can do this for you: ```js shell.chmod('+x', 'simple-script.sh'); shell.exec('sh ./simple-script.sh'); ```
Did you double check you're in the right working directory before calling `shell.exec()`? ``` console.log(`The current working directory is ${shell.pwd()}`); console.log(`Can shelljs see the file? ${shell.test('-f', 'simple-script.sh')}`); ``` If that's...
Sorry, this fell off my radar. I think you're right this could be a performance improvement, although this would be a fairly substantial architectural change. This would require rewriting all...
Have you tried https://github.com/MatthieuLemoine/shelljs-plugin-ssh? I'm not sure if that supports the right options, but if not you could open a feature request against that module. Your first thought isn't really...
Please include shelljs commands, including how you're trying to read the error code.
Works fine on my Mac OS system, same shelljs and node version. I don't see why ShellJS would mess up the exit code unless something really unexpected is going on....
What's the difference in the output? Can you post code?
Node version?
Confirmed as a bug. As a workaround, please use `child_process.execSync('npm init', {stdio: 'inherit'});` Fixes are welcomed.