Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-import-resolver-typescript 3.10.1 -> 4.4.4 age adoption passing 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

v3.10.1

Compare Source

v3.10.0

Compare Source

Minor Changes

Full Changelog: import-js/eslint-import-resolver-typescript@v3.9.1...v3.10.0

v3.9.1

Compare Source

Patch Changes

v3.9.0

Compare Source

Minor Changes

v3.8.7

Compare Source

Patch Changes

v3.8.6

Compare Source

Patch Changes

v3.8.5

Compare Source

Patch Changes

v3.8.4

Compare Source

Patch Changes

v3.8.3

Compare Source

Patch Changes

v3.8.2

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - "every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

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.

Copy link
Contributor Author

renovate bot commented Mar 21, 2025

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @scaleleap/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint-plugin-unicorn
npm ERR!   dev eslint-plugin-unicorn@"59.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev eslint-plugin-unicorn@"59.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=9.22.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-unicorn
npm ERR!     dev eslint-plugin-unicorn@"59.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-06-29T03_41_58_550Z-debug-0.log

@renovate renovate bot added the renovatebot label Mar 21, 2025
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 3 times, most recently from 3b8a4fa to da6a671 Compare March 29, 2025 22:03
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 2 times, most recently from 99f0d28 to 5da7628 Compare April 14, 2025 12:50
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 2 times, most recently from 7a25a9a to 266b737 Compare April 21, 2025 14:28
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from 266b737 to 4bee20a Compare April 28, 2025 14:07
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 2 times, most recently from f90a290 to 742821b Compare May 18, 2025 10:11
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 2 times, most recently from 09c187c to 310a4a3 Compare May 26, 2025 06:34
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 2 times, most recently from 89d6725 to afbb292 Compare June 6, 2025 15:58
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from afbb292 to 03cbc38 Compare June 29, 2025 03:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants