eslint-import-resolver-node@0.1.1 breaks build 🚨 #133
Closed
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
michaelfaith
pushed a commit
to michaelfaith/eslint-plugin-import
that referenced
this pull request
Sep 7, 2024
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.
Hello 👋
🚨🚨🚨
eslint-import-resolver-node just published its new version 0.1.1, which is covered by your current version range. After updating it in your project the build went from success to failure.
This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.
Happy fixing and merging 🌴
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡It keeps your software, up to date, all the time.