Support quoting scripts to run multiple scripts with the same process.env

[kentcdodds]

This passes all the tests, but I don't think that we should do this. cross-spawn does a LOT more than spawn-command. The only problem is that cross-spawn requires that the args are an array which would require parsing out the command. Unless there's a way to forward the whole string to a command and have that be evaluated... I think eval may work on unix, but what about windows?

Help needed!

[DanReyLop]

crossSpawn('cmd.exe', ['/s', '/c', theWholeCommand]) (works without the .exe too)

That should do the trick, it's basically what spawn-command does. Parsing the command is too big a complication to be worth it IMHO.

[kentcdodds]

Thanks for chiming in @DanReyLop. Hmmm... Not certain I follow though. Could you make a PR?

[DanReyLop]

I've hacked something together here. Obviously it's not production-ready, but it should illustrate my point. The idea is to wrap everything into a shell, so for example:
cross-env A=asdfg "ls . && ls ."
Output (Unix): sh -c "ls . && ls ."
Output (Win): cmd.exe /c "ls . && ls ."

Using eval (or CALL in Windows) doesn't work because it's a built-in shell command, not an executable command. Invoking a new shell is the closest thing available.

[DanReyLop]

Looking at cross-spawn I've realized there's a way easier solution, using spawn("the whole command", [], { shell: true }), but that was introduced in Node 4.8, so if you want to raise the minimum version required to run cross-env, it's up to you :)

[kentcdodds]

Sweet! I think that I'm good with raising the minimum requirement to 4.8. Most people should be there (or will be soon) anyway. Besides, the old cross-env works just fine :)

[hgwood]

#89 replaces this PR.