Skip to content
This repository has been archived by the owner on Oct 29, 2024. It is now read-only.

Avoid using && in package.json scripts. #270

Merged
merged 1 commit into from
Apr 4, 2020
Merged

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Apr 3, 2020

  • Using && locks us into specific shell support requirements which we don't really care about
  • Using npm-run-all will properly use yarn or npm depending on what is in use in the project.

* Using `&&` locks us into specific shell support requirements which we
  don't _really_ care about
* Using `npm-run-all` will properly use `yarn` or `npm` depending on
  what is in use in the project.
@pzuraq
Copy link
Member

pzuraq commented Apr 3, 2020

Does this preserve ordering of the logs in general? Just don't want to get the different outputs mixed up

@pzuraq pzuraq merged commit b499356 into master Apr 4, 2020
@pzuraq pzuraq deleted the avoid-shell-specifics branch April 4, 2020 03:29
@pzuraq
Copy link
Member

pzuraq commented Apr 4, 2020

Realized that the jobs in Actions were split up anyways, which is all I really cared about.

@rwjblue
Copy link
Member Author

rwjblue commented Apr 4, 2020

Does this preserve ordering of the logs in general? Just don't want to get the different outputs mixed up

Yes, it does not run them in parallel by default (though there is a way to do that) so the resulting log output is still in the correct order.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants