Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 24, 2025

This PR contains the following updates:

Package Change Age Confidence
ts-loader 9.5.2 -> 9.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


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.

Copy link
Contributor Author

renovate bot commented Aug 24, 2025

⚠️ 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.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @formatjs/[email protected]
npm error Found: [email protected]
npm error node_modules/typescript
npm error   typescript@"5.5.4" from the root project
npm error   peer typescript@">=4.2.0" from [email protected]
npm error   node_modules/ts-api-utils
npm error     ts-api-utils@"^1.3.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       dev @typescript-eslint/eslint-plugin@"7.18.0" from the root project
npm error     ts-api-utils@"^1.3.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/type-utils
npm error       @typescript-eslint/type-utils@"7.18.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"7.18.0" from the root project
npm error     2 more (@typescript-eslint/typescript-estree, @typescript-eslint/typescript-estree)
npm error   1 more (ts-loader)
npm error
npm error Could not resolve dependency:
npm error peerOptional typescript@"^5.6.0" from @formatjs/[email protected]
npm error node_modules/@formatjs/intl
npm error   @formatjs/intl@"3.1.6" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/typescript
npm error   peerOptional typescript@"^5.6.0" from @formatjs/[email protected]
npm error   node_modules/@formatjs/intl
npm error     @formatjs/intl@"3.1.6" 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-10-09T06_59_35_318Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-09T06_59_35_318Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ts-loader-9.x branch from 8d1a95e to db4a446 Compare September 4, 2025 10:55
@renovate renovate bot force-pushed the renovate/ts-loader-9.x branch 3 times, most recently from d7b713f to 8a412f4 Compare October 2, 2025 06:33
@renovate renovate bot force-pushed the renovate/ts-loader-9.x branch from 8a412f4 to 5d9b38a Compare October 9, 2025 06:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants