Command chaining, and separators broken

[purplecabbage]

The latest release has broken command interpretation.
Previously we used npm run-script to do the command processing for us, but changes to support long running processes also changed it so we are running the scripts ourselves. Our command interpretation only cares about spaces, and treats everything after the first space as an argument.

[[ "a" = "a" ]] && echo ok
echo it was okay > someFile.txt
cat package.json | jq .name

[aiojbot]

JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-949

[shazron]

There is an execa option that treats the whole string as a command: https://www.npmjs.com/package/execa#execacommandcommand-options

Will need to modify to use that and see if that fixes the issue.

[shazron]

@purplecabbage If we want to use shell specific features (like in your first example in the description with bash stuff) we need to enable the shell option in execa which comes with caveats: https://www.npmjs.com/package/execa#shell