Skip to content

chore(deps): update dependency ts-loader to v9.5.4#1646

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/ts-loader-9.x
Open

chore(deps): update dependency ts-loader to v9.5.4#1646
renovate[bot] wants to merge 1 commit intomainfrom
renovate/ts-loader-9.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 1, 2026

This PR contains the following updates:

Package Change Age Confidence
ts-loader 9.5.19.5.4 age confidence

Release Notes

TypeStrong/ts-loader (ts-loader)

v9.5.4

Compare Source

Skipping 9.5.3 due to a publishing issue

v9.5.2

Compare Source


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.

@renovate renovate bot requested review from a team as code owners April 1, 2026 21:51
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Apr 1, 2026

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-auto-mock@3.7.4
npm error Found: typescript@4.9.5
npm error node_modules/typescript
npm error   dev typescript@"4.9.5" from the root project
npm error   peer typescript@">=3.8 <5.0" from ts-jest@27.1.5
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^27.0.4" from the root project
npm error   4 more (ts-node, tsutils, ttypescript, ts-loader)
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.0.4" from ts-auto-mock@3.7.4
npm error node_modules/ts-auto-mock
npm error   dev ts-auto-mock@"^3.3.5" from the root project
npm error   peer ts-auto-mock@"^3.5.0" from jest-ts-auto-mock@2.1.0
npm error   node_modules/jest-ts-auto-mock
npm error     dev jest-ts-auto-mock@"^2.0.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@"^5.0.4" from ts-auto-mock@3.7.4
npm error   node_modules/ts-auto-mock
npm error     dev ts-auto-mock@"^3.3.5" from the root project
npm error     peer ts-auto-mock@"^3.5.0" from jest-ts-auto-mock@2.1.0
npm error     node_modules/jest-ts-auto-mock
npm error       dev jest-ts-auto-mock@"^2.0.0" 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/2026-04-02T08_59_38_979Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-02T08_59_38_979Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ts-loader-9.x branch from a0eb34c to eb950ec Compare April 2, 2026 08:59
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.

0 participants