chore: release eslint-import-resolver-typescript #388
Merged
+11
−10
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
eslint-import-resolver-typescript@4.1.0
Minor Changes
#387
ef5cd10
Thanks @JounQin! - feat: add a newbun?: boolean
option forbun
users - close Unable to resolve path to module 'bun:test' with 4.0.0 while 3.9.1 is OK #386process.versions.bun
is unavailable even withbun eslint
due to its own design,but checking
bun
modules for non-bun users is incorrect behavior and just wasting time,so a new option is added for such case, you can still run with
bun --bun eslint
without this option enabled