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 contains the following updates:
^4.5.0
->^4.6.1
^8.18.0
->^8.18.1
Release Notes
un-ts/eslint-plugin-import-x (eslint-plugin-import-x)
v4.6.1
Compare Source
Patch Changes
be9c3e8
Thanks @mrginglymus! - Fix enhanced-resolve dependencyv4.6.0
Compare Source
Minor Changes
#209
46d2360
Thanks @SukkaW! - Wheneslint-plugin-import-x
was forked fromeslint-plugin-import
, we copied over the default resolver (which iseslint-import-resolver-node
) as well. However, this resolver doesn't supportsexports
in thepackage.json
file, and the current maintainer of theeslint-import-resolver-node
(ljharb) doesn't have the time implementing this feature and he locked the issue https://github.com/import-js/eslint-plugin-import/issues/1810.So we decided to implement our own resolver that "just works". The new resolver is built upon the
enhanced-resolve
that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #192.In the next major version of
eslint-plugin-import-x
, we will remove theeslint-import-resolver-node
and use this new resolver by default. In the meantime, you can try out this new resolver by setting theimport-x/resolver-next
option in youreslint.config.js
file:We do not plan to implement reading
baseUrl
andpaths
from thetsconfig.json
file in this resolver. If you need this feature, please checkout eslint-import-resolver-typescript (also powered byenhanced-resolve
), eslint-import-resolver-oxc (powered byoxc-resolver
), eslint-import-resolver-next (also powered byoxc-resolver
), or other similar resolvers.Patch Changes
449738f
Thanks @privatenumber! - insert type prefix without new linev4.5.1
Compare Source
Patch Changes
#198
ac6d2e1
Thanks @voxpelli! - Fix #197 with missing types#204
32e9b55
Thanks @privatenumber! - fix type-import and value-import merging when import-as is usedtypescript-eslint/typescript-eslint (typescript-eslint)
v8.18.1
Compare Source
This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.