Make yarn tasks imply yarn install where appropriate
#11394
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sean-mcmanus
previously approved these changes
Aug 31, 2023
Colengms
reviewed
Aug 31, 2023
…nto garretts/yarn-tasks-imply-install
Colengms
approved these changes
Sep 5, 2023
michelleangela
approved these changes
Sep 5, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After chatting with @Colengc and @sean-mcmanus about implied
yarn installI've refactored the scripts a bit more inpackage.jsonand nowcompileandwatchandwebpackand others will callyarn install(which in itself is very fast) -- and will verify the prep steps and run those only if necessary. (which are slower, and less like to be needed to run often)