Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency eslint-import-resolver-typescript to v4 #1296

Merged
merged 1 commit into from
Mar 17, 2025

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 17, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-import-resolver-typescript 3.9.1 -> 4.1.1 age adoption passing confidence

Release Notes

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

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

Sorry, something went wrong.

Copy link

codecov bot commented Mar 17, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (aa64db7) to head (2cdbda9).
Report is 2 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1296   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          339       339           
  Branches        44        44           
=========================================
  Hits           339       339           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from 267d7ec to 0bd929f Compare March 17, 2025 17:25
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from 0bd929f to 89e52ce Compare March 17, 2025 18:00
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-typescript-4.x branch from 89e52ce to 2cdbda9 Compare March 17, 2025 18:04
@kristof-mattei kristof-mattei merged commit 4e2101b into main Mar 17, 2025
11 checks passed
@kristof-mattei kristof-mattei deleted the renovate/eslint-import-resolver-typescript-4.x branch March 17, 2025 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant