This repository was archived by the owner on Apr 4, 2023. It is now read-only.
Fix after-prepare hook doesn't check if release build to determine env #1774
Conversation
This file contains hidden or 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
delaneyb
changed the title
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.
The current after-prepare hook's check to determine what env - 'production' or 'development' - it is building for does not match the check used in the before-checkForChanges hook. Specifically, it does not identify we are performing a production build if the release flag is set, unless env.production or env.prod are specified.
I have also simplified and made sure the way isProdEnv and isStagingEnv are computed is consistent across the two scripts.