chore(nx): bust build cache on babel config change #6443
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
jtoar
added
topic/ops-&-contributing-dx
release:chore
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
see: https://nx.dev/reference/nx-json#inputs-&-namedinputs
color
nxuses caching to determine which steps to do/not do when running something likeyarn buildOut of the box it does it's best to determine which changes correctly trigger a rebuild, however it doesn't really account for config files such as a babel config.
Changes to the babel config file, need to bust the build cache as they can have a huge effect on the built artifacts given we use babel to build our JS. This PR ensures that changes to the babel config, correctly allow for a rebuild of the framework.