Bump eslint-import-resolver-typescript from 3.6.1 to 4.2.2

[dependabot]

Bumps eslint-import-resolver-typescript from 3.6.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)
• 14a7688 chore: bump rspack-resolver for better P'n'P support (#397)
• 0adca68 chore: release eslint-import-resolver-typescript (#395)
• 9f11f6b fix: don't set empty configFile when no tsconfig found (#394)
• 3b0edff chore: release eslint-import-resolver-typescript (#392)
• 490ca12 docs: clarify this is a resolver not plugin
• c8121e5 feat: make is-bun-module as optional peer dependency (#391)
• 458fdaf chore: release eslint-import-resolver-typescript (#390)
• 1b97d8a fix: should prefer module.isBuiltin when process.versions.bun available (...
• 79a453b chore: release eslint-import-resolver-typescript (#388)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.