You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 22, 2018. It is now read-only.
The sequence API is kinda weird, in that you usually end up passing an array of words broken by spaces, for example ['npm', 'install'].
I've yet to see a use case that breaks that pattern, actually.
We could save users some keystrokes (and headaches) by allowing them to pass in a string (for example, npm install, which will be broken down into the command and array of arguments to be passed into exec behind the scenes.
The text was updated successfully, but these errors were encountered:
As of d6772b2, we prefer sequences to be arrays of strings, not arrays of arrays as before. It helps that child_process.exec, which we adopted in #1, accepts commands with arguments as a single string.
This is simpler, easier to type, and easier to read when editing a target!
I've added in legacy support for arrays for backwards compatibility- this will be removed...someday....
The sequence API is kinda weird, in that you usually end up passing an array of words broken by spaces, for example
['npm', 'install']
.I've yet to see a use case that breaks that pattern, actually.
We could save users some keystrokes (and headaches) by allowing them to pass in a string (for example,
npm install
, which will be broken down into the command and array of arguments to be passed into exec behind the scenes.The text was updated successfully, but these errors were encountered: