don't use babel-plugin-module-resolver@5.0.1 #1884
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
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.
babel-plugin-module-resover released an update yesterday that bumped some dependencies, but it was released as a patch but the dependencies were major bumps (that dropped support for Node 16 馃檲 )
I have opened a PR upstream to fix the issue tleunen/babel-plugin-module-resolver#446
but for now this PR to pin will fix our CI. I have limited it to only the bad version so that we can still get the next release and hopefully it will have fixed the issue. If not then we can widen the version range to pin all bad versions 馃憤