Skip to content

fix(deps): update dependency eslint-import-resolver-typescript to v4#712

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-import-resolver-typescript-4.x
Open

fix(deps): update dependency eslint-import-resolver-typescript to v4#712
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-import-resolver-typescript-4.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Feb 16, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint-import-resolver-typescript ^3.0.0^4.0.0 age confidence

Release Notes

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

v4.4.4

Compare Source

Patch Changes

v4.4.3

Compare Source

Patch Changes

v4.4.2

Compare Source

Patch Changes

v4.4.1

Compare Source

Patch Changes

v4.4.0

Compare Source

Minor Changes

v4.3.5

Compare Source

Patch Changes

v4.3.4

Compare Source

Patch Changes

v4.3.3

Compare Source

Patch Changes

v4.3.2

Compare Source

Patch Changes

v4.3.1

Compare Source

Patch Changes

v4.3.0

Compare Source

Minor Changes

v4.2.7

Compare Source

Patch Changes

v4.2.6

Compare Source

Patch Changes

v4.2.5

Compare Source

Patch Changes

v4.2.4

Compare Source

Patch Changes
  • #​407 6b183ff Thanks @​JounQin! - chore: migrate to rebranding unrs-resolver with new targets supported:

    • i686-pc-windows-msvc
    • armv7-unknown-linux-musleabihf
    • powerpc64le-unknown-linux-gnu
    • s390x-unknown-linux-gnu

v4.2.3

Compare Source

Patch Changes
  • #​402 f21bf15 Thanks @​SunsetTechuila! - fix: don't resolve not implemented node modules in bun

    is-bun-module is marked as dependency, again, for correctness, see isBunImplementedNodeModule for more details

    For Bun users: you don't need to install is-bun-module any more but bun: true option is still required if you're running without bun --bun nor run#bun enabled

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

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

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

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 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.

🔕 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.

@renovate renovate Bot requested a review from a team as a code owner February 16, 2026 02:55
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Feb 16, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @netlify/eslint-config-node@7.0.1
npm error Found: @typescript-eslint/utils@5.62.0
npm error node_modules/@typescript-eslint/utils
npm error   @typescript-eslint/utils@"5.62.0" from @typescript-eslint/eslint-plugin@5.62.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     @typescript-eslint/eslint-plugin@"^5.0.0" from the root project
npm error   @typescript-eslint/utils@"5.62.0" from @typescript-eslint/type-utils@5.62.0
npm error   node_modules/@typescript-eslint/type-utils
npm error     @typescript-eslint/type-utils@"5.62.0" from @typescript-eslint/eslint-plugin@5.62.0
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       @typescript-eslint/eslint-plugin@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error eslint-import-resolver-typescript@"^4.0.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/utils@8.59.1
npm error node_modules/@typescript-eslint/utils
npm error   peerOptional @typescript-eslint/utils@"^8.56.0" from eslint-plugin-import-x@4.16.2
npm error   node_modules/eslint-plugin-import-x
npm error     peerOptional eslint-plugin-import-x@"*" from eslint-import-resolver-typescript@4.4.4
npm error     node_modules/eslint-import-resolver-typescript
npm error       eslint-import-resolver-typescript@"^4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-04-29T17_38_27_283Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-29T17_38_27_283Z-debug-0.log

@renovate renovate Bot added the javascript label Feb 16, 2026
@github-actions github-actions Bot added the type: bug code to address defects in shipped code label Feb 16, 2026
@renovate renovate Bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from e2f21f5 to e9cf6d2 Compare March 5, 2026 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies javascript type: bug code to address defects in shipped code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants