directory-connector
directory-connector copied to clipboard
[deps]: Update eslint-import-resolver-typescript to v3.10.1
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| eslint-import-resolver-typescript | 3.7.0 -> 3.10.1 |
Release Notes
import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)
v3.10.1
v3.10.0
Minor Changes
-
#413
89c2795Thanks @JounQin! - chore: housekeeping, bump all (dev) depsMigrate
rspack-resolverto rebrandingunrs-resolverfor more targets support and other bug fixes
Full Changelog: https://github.com/import-js/eslint-import-resolver-typescript/compare/v3.9.1...v3.10.0
v3.9.1
Patch Changes
- #382
4a9176eThanks @JounQin! - fix: userspack-resolverfork for pnp support
v3.9.0
Minor Changes
v3.8.7
Patch Changes
- #377
a14fdd9Thanks @carlocorradini! - fix: include mapper with no files and force non-dynamic projects to use absolute paths
v3.8.6
Patch Changes
v3.8.5
Patch Changes
- #372
366eeafThanks @carlocorradini! - fix: if file has no corresponding mapper function, apply all of them, starting with the nearest one.
v3.8.4
Patch Changes
v3.8.3
Patch Changes
-
#360
8192976Thanks @carlocorradini! - Force tiniglobby to expand dot directories -
#360
8192976Thanks @carlocorradini! - Update tinyglobby to latest version
v3.8.2
Patch Changes
- #357
5fd349eThanks @carlocorradini! - Update thetinyglobbyto the latest version to solve performance regressions.
v3.8.1
Patch Changes
- #352
0c6303dThanks @carlocorradini! - Set cwd while resolving tsconfig include
v3.8.0
Minor Changes
-
#345
fcc8883Thanks @carlocorradini! - Enable the mapper function just for a set of allowed files. Improves project discovery using glob and POSIX separator. -
#346
c124e87Thanks @carlocorradini! - Update get-tsconfig to the the latest version. We now support the${configDir}variable, introduced in TypeScript 5.5.
Configuration
📅 Schedule: Branch creation - "every 2nd week starting on the 2 week of the year before 4am on Monday" (UTC), 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.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 7.74%. Comparing base (
1deb22a) to head (afbef32).
:white_check_mark: All tests successful. No failed tests found.
Additional details and impacted files
@@ Coverage Diff @@
## main #754 +/- ##
=====================================
Coverage 7.74% 7.74%
=====================================
Files 68 68
Lines 2751 2751
Branches 473 473
=====================================
Hits 213 213
Misses 2523 2523
Partials 15 15
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
Internal tracking:
- ID: PM-20708
- Link: https://bitwarden.atlassian.net/browse/PM-20708
⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @bitwarden/[email protected]
npm error Found: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error @typescript-eslint/utils@"7.11.0" from @angular-eslint/[email protected]
npm error node_modules/@angular-eslint/eslint-plugin-template
npm error dev @angular-eslint/eslint-plugin-template@"17.5.3" from the root project
npm error @typescript-eslint/utils@"7.11.0" from @angular-eslint/[email protected]
npm error node_modules/@angular-eslint/utils
npm error @angular-eslint/utils@"17.5.3" from @angular-eslint/[email protected]
npm error node_modules/@angular-eslint/eslint-plugin-template
npm error dev @angular-eslint/eslint-plugin-template@"17.5.3" from the root project
npm error 1 more (@typescript-eslint/type-utils)
npm error
npm error Could not resolve dependency:
npm error dev eslint-import-resolver-typescript@"3.10.1" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/[email protected]
npm error node_modules/@typescript-eslint/utils
npm error peerOptional @typescript-eslint/utils@"^8.0.0" from [email protected]
npm error node_modules/eslint-plugin-import-x
npm error peerOptional eslint-plugin-import-x@"*" from [email protected]
npm error node_modules/eslint-import-resolver-typescript
npm error dev eslint-import-resolver-typescript@"3.10.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-07-01T03_18_53_913Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-07-01T03_18_53_913Z-debug-0.log
This has a conflicting peer dependency:
@angular-eslint/[email protected]requires@typescript-eslint/utils@"7.11.0"- but
eslint-import-resolver-typescript@"3.10.1"(this update) requires@typescript-eslint/utils@"^8.0.0"
The fix is to upgrade Angular so that it's also using a newer version of the utils package, which requires upgrading to at least 18. Angular 17 is no longer supported, so we should do that. See https://github.com/bitwarden/directory-connector/pull/805
Closing until we upgrade Angular.
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (3.10.1). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.