#368 chore(deps-dev): bump eslint-import-resolver-typescript from 3.9.1 to 4.2.2 Pull request opened by dependabot[bot] Bumps eslint-import-resolver-typescript from 3.9.1 to 4.2.2. Release notes Sourced from eslint-import-resolver-typescript's releases.

## v4.2.2

### 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

### 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

### 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

### Patch Changes

• #389 `1b97d8a` Thanks `@​JounQin`! - fix: should prefer

module.isBuiltin

when

process.versions.bun

available

## v4.1.0

### 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

### 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

... (truncated) Changelog Sourced from eslint-import-resolver-typescript's changelog.

## 4.2.2

### Patch Changes

• #397 `14a7688` Thanks `@​JounQin`! - chore: bump

rspack-resolver

for better P'n'P support

Now

rspack-resolver

resolves

pnpapi

natively.

## 4.2.1

### 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

## 4.2.0

### 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

## 4.1.1

### Patch Changes

• #389 `1b97d8a` Thanks `@​JounQin`! - fix: should prefer

module.isBuiltin

when

process.versions.bun

available

## 4.1.0

### 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

## 4.0.0

### Major Changes

... (truncated) Commits • `288c53c` chore: release eslint-import-resolver-typescript (#398) • <https://github.com/import-js/eslint-import-resolver-type… pact-foundation/jest-pact