chore: bump unrs-resolver to v1.6.2 to fix false positive lint error
#86
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
mkosir
approved these changes
Apr 21, 2025
|
Hey @JounQin, huge thanks for the PR! 🚀 |
|
🎉 This PR is included in version 1.7.292 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
|
I totally missed it, upgrading to that sounds awesome. Feel free to open a PR for it 🙌 |
Here we go: #87 |
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.
🚀 Pull Request Template
Description
close import-js/eslint-import-resolver-typescript#437
Checklist
npm run commitnpm run lint && npm run tsc && npm run test-reportBy the way, I recommend you to migrate
eslint-plugin-importto modern and faster https://github.com/un-ts/eslint-plugin-import-x, I can raise a PR for you if you agree.