Nate Fischer
Nate Fischer
@MatthieuLemoine > The main problem is that i can't understand why you have to build a script in a script. execSync can run a command. This is a pretty ancient...
I added the workaround to the FAQs: https://github.com/shelljs/shelljs/wiki/FAQ#running-interactive-programs-with-exec
@RastogiAbhijeet https://github.com/shelljs/shelljs/wiki/FAQ#running-interactive-programs-with-exec
I'd like to revive this, since I'm a fan of async shell scripting. I'll probably implement a PR along the lines that @mstade suggested, since I actually like the precedent...
@ariporad does that approach involve modifying the interface to the functions? I'd really like something like: ``` javascript require('shelljs'); cp('smallfile.txt', 'out1.txt'); // synchronous cp('largefile.txt', 'out2.txt', function(code, stdout, stderr) { if...
I'm very against making things async by default. ShellJS is a really nice way to rewrite shell scripts into JavaScript. Bash is sync by default, so shelljs should be the...
#387 is an initial stab at how I see the API looking/working. Take a look, let me know what you all think :+1:
@corbinu we still support Node 4. I haven't used async/await much--which node versions support them?
@corbinu thanks! We've been trying to match our support back to supported node versions. We don't have a hard rule, but we may drop support for releases sometime during maintenance...
This is cool, maybe we could add a "promise: true" option to shell.exec? That would be backwards compatible, but could be awaited by users to emulate exec-sync.