⬆️ Updates eslint-import-resolver-typescript to v4 #884

renovate · 2025-03-22T08:11:36Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-import-resolver-typescript	`^2.0.0` -> `^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

`v3.8.3`

Compare Source

Patch Changes

#360 8192976 Thanks @carlocorradini! - Force tiniglobby to expand dot directories
#360 8192976 Thanks @carlocorradini! - Update tinyglobby to latest version

`v3.8.2`

Compare Source

Patch Changes

#357 5fd349e Thanks @carlocorradini! - Update the tinyglobby to the latest version to solve performance regressions.

`v3.8.1`

Compare Source

Patch Changes

#352 0c6303d Thanks @carlocorradini! - Set cwd while resolving tsconfig include

`v3.8.0`

Compare Source

Minor Changes

#345 fcc8883 Thanks @carlocorradini! - Enable the mapper function just for a set of allowed files. Improves project discovery using glob and POSIX separator.
#346 c124e87 Thanks @carlocorradini! - Update get-tsconfig to the the latest version. We now support the ${configDir} variable, introduced in TypeScript 5.5.

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

`v3.5.2`

Compare Source

Patch Changes

#193 8756a26 Thanks @Rialgar! - chore(package): remove node 12 from engines field
#187 7a91daf Thanks @scott-ut! - fix: resolve modules if folder contains a package.json file

`v3.5.1`

Compare Source

Patch Changes

#182 afeb928 Thanks @chenxinyanc! - perf: disable throwIfNoEntry on Node 14+

`v3.5.0`

Compare Source

Minor Changes

#174 66a3e6c Thanks @JounQin! - feat: reuse eslint-module-utils/hash.js for better caching

Patch Changes

#172 00abb6f Thanks @JounQin! - fix: incorrect exports mapping

`v3.4.2`

Compare Source

Patch Changes

594df9c Thanks @HanSeo0507! - chore(deps): update dependency synckit to ^0.8.3 for yarn PnP (#169)

`v3.4.1`

Compare Source

Patch Changes

#166 8892a8c Thanks @thatsmydoing! - perf: add filesystem caching support

`v3.4.0`

Compare Source

Minor Changes

#161 82d090b Thanks @rbong! - feat: add support for jsconfig.json

`v3.3.0`

Compare Source

Minor Changes

#154 42f2dd6 Thanks @JounQin! - feat: add externsionAlias option support, .d.([cm]?ts|tsx) are always preferred than .([cm]?js|jsx)

typescript resolves typescript/lib/typescript.d.ts instead of typescript/lib/typescript.js by default
#154 42f2dd6 Thanks @JounQin! - feat: exports globSync, defaultExtensions, defaultMainFields, defaultConditionNames and defaultExtensionAlias for reusing

Patch Changes

#154 42f2dd6 Thanks @JounQin! - perf: cache options and resolver
#154 42f2dd6 Thanks @JounQin! - chore: align with Angular Package Format correctly

reference: https://angular.io/guide/angular-package-format
#156 4bd60c3 Thanks @JounQin! - docs: document options from enhanced-resolve

`v3.2.7`

Compare Source

Patch Changes

60ff431 Thanks @JounQin! - chore: bump synckit

`v3.2.6`

Compare Source

Patch Changes

#146 7edb823 Thanks @JounQin! - chore: use latest get-tsconfig package

`v3.2.5`

Compare Source

Patch Changes

#136 abf8907 Thanks @JounQin! - build: use pnpm as manager, yarn pnp is still supported

`v3.2.4`

Compare Source

Patch Changes

#139 3e93659 Thanks @JounQin! - fix: run prerelease manually for yarn v3, 2nd try

`v3.2.2`

Compare Source

Patch Changes

#133 d944b26 Thanks @JounQin! - fix: use yarn v3 with PnP linker, close #130

`v3.2.1`

Compare Source

Patch Changes

#131 fb88af2 Thanks @JounQin! - fix: try index file with extensions automatically

`v3.2.0`

Compare Source

Minor Changes

#128 56775b3 Thanks @JounQin! - refactor: support custom extensions on resolving
#128 56775b3 Thanks @JounQin! - feat: try extensionless file by default

`v3.1.5`

Compare Source

Patch Changes

#126 9cf60cb Thanks @JounQin! - fix: auto try extensions

`v3.1.4`

Compare Source

Patch Changes

f88a8c9 Thanks @JounQin! - refactor: use non-capturing groups for perf

`v3.1.3`

Compare Source

Patch Changes

#121 35d3022 Thanks @JounQin! - fix: try index.d.ts automatically

`v3.1.2`

Compare Source

Patch Changes

#118 01f525e Thanks @JounQin! - docs: update repository, document exports support

3.1.1 (2022-06-27)

Bug Fixes

add conditionNames support (#114) (c74fe0e)

`v3.1.1`

Compare Source

`v3.1.0`

Compare Source

⚠ BREAKING CHANGES

use enhanced-resolve instead

Features

support angular-package-format out of box (7e0cd04)
use enhanced-resolve instead (39ab8b1), closes #85 #107

`v3.0.0`

Compare Source

⚠ BREAKING CHANGES

remove depracated directory option
use get-tsconfig to replace tsconfig-paths
bump globby, use synckit for sync fn
deps: bump tsconfig-paths to ^4.0.0 (#104)

Features

bump globby, use synckit for sync fn (322cb29)
ignore node_modules folder in projects option glob (#105) (1e1b5a6)
remove depracated directory option (67c8d59)
use get-tsconfig to replace tsconfig-paths (78a08e0)
deps: bump tsconfig-paths to ^4.0.0 (#104) (b2edbc8)

2.7.1 (2022-04-03)

Bug Fixes

per package.json warning (#101) (664465f)

`v2.7.1`

Compare Source

`v2.7.0`

Compare Source

Features

support .cjs .mjs .cts .mts extensions (#84) (1e39028)

`v2.6.0`

Compare Source

Bug Fixes

upgrade (dev)Dependencies (#99) (2e7b4f4)

`v2.5.0`

Compare Source

Features

allow passing through custom options to resolve (#79) (34c94c8)

Bug Fixes

bump (dev)Dependencies, apply stricter rules (#75) (866f32f)

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

github-actions · 2025-03-22T08:11:47Z

Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md.

github-actions · 2025-03-22T08:11:47Z

Hello from PR Helper

Is your PR ready for review and processing? Mark the PR ready by including #pr-ready in a comment.

If you still have work to do, even after marking this ready. Put the PR on hold by including #pr-onhold in a comment.

github-actions · 2025-03-22T08:11:51Z

Thanks for the PR!

This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged.

socket-security · 2025-03-22T08:12:05Z

Report too large to display inline

View full report↗︎

socket-security · 2025-03-22T08:12:06Z

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/minimist@1.2.5	CVE: GHSA-xvch-5gv4-984h Prototype Pollution in minimist (CRITICAL) Affected versions: >= 1.0.0, < 1.2.6 Patched version: 1.2.6	`package-lock.json`	⚠︎
Critical CVE	npm/json-schema@0.2.3	CVE: GHSA-896r-f27r-55mw json-schema is vulnerable to Prototype Pollution (CRITICAL) Affected versions: < 0.4.0 Patched version: 0.4.0	`package-lock.json`	⚠︎
Critical CVE	npm/underscore@1.7.0	CVE: GHSA-cf4h-3jhx-xvhq Arbitrary Code Execution in underscore (CRITICAL) Affected versions: >= 1.3.2, < 1.12.1 Patched version: 1.12.1	`package-lock.json`	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

@SocketSecurity ignore npm/minimist@1.2.5
@SocketSecurity ignore npm/json-schema@0.2.3
@SocketSecurity ignore npm/underscore@1.7.0

⬆️ Updates eslint-import-resolver-typescript to v4

10d078d

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot added the npm dependencies label Mar 22, 2025

auto-assign bot requested a review from AlexRogalskiy March 22, 2025 08:11

github-actions bot added the review-required label Mar 22, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

⬆️ Updates eslint-import-resolver-typescript to v4 #884

⬆️ Updates eslint-import-resolver-typescript to v4 #884

renovate bot commented Mar 22, 2025

github-actions bot commented Mar 22, 2025

github-actions bot commented Mar 22, 2025

github-actions bot commented Mar 22, 2025

socket-security bot commented Mar 22, 2025

socket-security bot commented Mar 22, 2025

⬆️ Updates eslint-import-resolver-typescript to v4 #884

Are you sure you want to change the base?

⬆️ Updates eslint-import-resolver-typescript to v4 #884

Conversation

renovate bot commented Mar 22, 2025

Release Notes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Major Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

3.1.1 (2022-06-27)

Bug Fixes

⚠ BREAKING CHANGES

Features

⚠ BREAKING CHANGES

Features

2.7.1 (2022-04-03)

Bug Fixes

Features

Bug Fixes

Features

Bug Fixes

Configuration

github-actions bot commented Mar 22, 2025

github-actions bot commented Mar 22, 2025

Hello from PR Helper

github-actions bot commented Mar 22, 2025

socket-security bot commented Mar 22, 2025

socket-security bot commented Mar 22, 2025

Next steps