chore(deps): update dependency eslint-import-resolver-typescript to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-import-resolver-typescript	^3.8.3 -> ^4.0.0

---

Release Notes

import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)

v4.2.2

Compare Source

Patch Changes

• #​397 14a7688 Thanks @​JounQin! - chore: bump rspack-resolver for better P'n'P support

  Now rspack-resolver resolves pnpapi natively.

v4.2.1

Compare Source

Patch Changes

• #​394 9f11f6b Thanks @​JounQin! - fix: don't set empty configFile when no tsconfig found

• #​394 9f11f6b Thanks @​JounQin! - chore: bump rspack-resolver to v1.2.0

v4.2.0

Compare Source

Minor Changes

• #​391 c8121e5 Thanks @​JounQin! - feat: make is-bun-module as optional peer dependency

  Technically this is a BREAKING CHANGE, but considering we just raise out v4 recently and this only affects bun users, bun --bun eslint even works without this dependency, so I'd consider this as a minor change.

  So for bun users, there are three options:

  1. install is-bun-module dependency manually and use bun: true option
  2. run eslint with bun --bun eslint w/o bun: true option
  3. enable run#bun in bunfig.toml w/o bun: true option

v4.1.1

Compare Source

Patch Changes

• #​389 1b97d8a Thanks @​JounQin! - fix: should prefer module.isBuiltin when process.versions.bun available

v4.1.0

Compare Source

Minor Changes

• #​387 ef5cd10 Thanks @​JounQin! - feat: add a new bun?: boolean option for bun users - close #​386

  process.versions.bun is unavailable even with bun 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

v4.0.0

Compare Source

Major Changes

• #​368 2fd7c2e Thanks @​JounQin! - feat!: rewrite, speed up by using rspack-resolver which supports references natively under the hood

  BREAKING CHANGES:

  • drop Node 14 support, Node ^16.17.0 || >=18.6 is now required
  • alwaysTryTypes is enabled by default, you can set it as false to opt-out
  • array type of project is discouraged but still supported, single project with references are encouraged for better performance, you can enable noWarnOnMultipleProjects option to supress the warning message
  • root tsconfig.json or jsconfig.json will be used automatically if no project provided

v3.9.1

Compare Source

Patch Changes

• #​382 4a9176e Thanks @​JounQin! - fix: use rspack-resolver fork for pnp support

v3.9.0

Compare Source

Minor Changes

• #​379 6814443 Thanks @​JounQin! - feat: migrate enhanced-resolve to oxc-resolver

v3.8.7

Compare Source

Patch Changes

• #​377 a14fdd9 Thanks @​carlocorradini! - fix: include mapper with no files and force non-dynamic projects to use absolute paths

v3.8.6

Compare Source

Patch Changes

• #​374 c9d5ab0 Thanks @​JounQin! - fix: add support for importing with .js extension as tsx importee

v3.8.5

Compare Source

Patch Changes

• #​372 366eeaf Thanks @​carlocorradini! - fix: if file has no corresponding mapper function, apply all of them, starting with the nearest one.

v3.8.4

Compare Source

Patch Changes

• #​370 c940785 Thanks @​JounQin! - fix: support multiple matching ts paths

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[netlify]

❌ Deploy Preview for jestjs failed.

Name	Link
🔨 Latest commit	4f96077
🔍 Latest deploy log	https://app.netlify.com/sites/jestjs/deploys/67d7841af710a900084fa03c

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.