Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 10, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-import-resolver-typescript ^3.8.3 -> ^4.0.0 age adoption passing confidence

Release Notes

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

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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 added the types label May 10, 2025
@renovate
Copy link
Contributor Author

renovate bot commented May 10, 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: yarn.lock
➤ YN0000: · Yarn 4.2.2
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: @auto-files/rpc-apis@workspace:*: Workspace not found (@auto-files/rpc-apis@workspace:*)
    at St.getWorkspaceByDescriptor (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:210:3520)
    at l1.getCandidates (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:140:115276)
    at Pd.getCandidates (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:141:1311)
    at Pd.getCandidates (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:141:1311)
    at /tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:210:8409
    at Ky (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:140:53916)
    at Fe (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:210:8389)
    at async Promise.allSettled (index 1)
    at async _c (/tmp/containerbase/cache/.cache/node/corepack/v1/yarn/4.2.2/yarn.js:140:53244)
➤ YN0000: └ Completed in 0s 948ms
➤ YN0000: · Failed with errors in 0s 973ms

@netlify
Copy link

netlify bot commented May 10, 2025

Deploy Preview for auto-drive-demo failed. Why did it fail? →

Name Link
🔨 Latest commit 8422b87
🔍 Latest deploy log https://app.netlify.com/projects/auto-drive-demo/deploys/684c467d3a165e0008cf7db5

@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 10 times, most recently from 9e26ac3 to 600bc87 Compare May 19, 2025 12:19
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 6 times, most recently from 9161e1b to 35e0e1c Compare May 26, 2025 10:18
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 6 times, most recently from e57458c to 931c3fe Compare June 3, 2025 13:02
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 3 times, most recently from 4a36692 to 8f78472 Compare June 6, 2025 13:33
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from 8f78472 to 4e33cbe Compare June 10, 2025 11:47
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch 4 times, most recently from 46f9068 to d9812c6 Compare June 11, 2025 21:58
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from d9812c6 to 8422b87 Compare June 13, 2025 15:40
@clostao clostao closed this Jun 16, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Jun 16, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/eslint-import-resolver-typescript-4.x branch June 16, 2025 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants