⬆️ Update dependency eslint-import-resolver-typescript to ^3.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-import-resolver-typescript	^3.5.2 -> ^3.7.0

---

Release Notes

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

v3.7.0

Compare Source

Minor Changes

• #​326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

  Previously

  // eslint.config.js
  module.exports = {
    settings: {
      'import-x/resolver': {
        typescript: {
          alwaysTryTypes: true,
        },
        // or
        require.resolve('eslint-import-resolver-typescript'):
          alwaysTryTypes: true,
        }
      }
    }
  }

  Now

  // eslint.config.js
  const {
    createTypeScriptImportResolver,
  } = require('eslint-import-resolver-typescript')
  
  module.exports = {
    settings: {
      'import-x/resolver-next': [
        createTypeScriptImportResolver({
          alwaysTryTypes: true,
        }),
      ],
    },
  }

  Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

v3.6.3

Compare Source

Patch Changes

• #​305 f8d7b82 Thanks @​SukkaW! - Fix resolve for node:test, node:sea, and node:sqlite without sacrificing installation size

• #​288 a4c6c78 Thanks @​SunsetTechuila! - fix: ignore bun built-in modules

v3.6.1

Compare Source

Patch Changes

• #​241 cf5d67f Thanks @​klippx! - Fix CJS import to make it compatible with ESM projects

v3.6.0

Compare Source

Minor Changes

• #​235 b5ea367 Thanks @​SukkaW! - refactor: drop globby and synckit

v3.5.5

Compare Source

Patch Changes

• 84b0649 Thanks @​JounQin! - fix: mark eslint-module-utils as dep

v3.5.4

Compare Source

Patch Changes

• 25f3920 Thanks @​JounQin! - fix: enhanced-resolve is commonjs only - close #​213

• #​219 0bf6ffb Thanks @​lsmurray! - fix: check if cwd changed to bust mapper cache

v3.5.3

Compare Source

Patch Changes

• #​206 6531bad Thanks @​marvinhagemeister! - Only try to resolve a module directory when we know that the path is a directory. This can lead to a 15% speedup on projects with many files.

---

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.

[renovate]

⚠️ 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: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^7.5.0 || ^8.0.0" from @babel/[email protected]
npm ERR!   node_modules/@babel/eslint-parser
npm ERR!     peer @babel/eslint-parser@"^7.16.5" from @nextcloud/[email protected]
npm ERR!     node_modules/@nextcloud/eslint-config
npm ERR!       dev @nextcloud/eslint-config@"^8.2.1" from the root project
npm ERR!   peer eslint@"^8.27.0" from @nextcloud/[email protected]
npm ERR!   node_modules/@nextcloud/eslint-config
npm ERR!     dev @nextcloud/eslint-config@"^8.2.1" from the root project
npm ERR!   16 more (@nextcloud/eslint-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev eslint-import-resolver-typescript@"^3.7.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^8.57.0 || ^9.0.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-import-x
npm ERR!     peerOptional eslint-plugin-import-x@"*" from [email protected]
npm ERR!     node_modules/eslint-import-resolver-typescript
npm ERR!       dev eslint-import-resolver-typescript@"^3.7.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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-03T17_04_24_730Z-debug-0.log