Skip to content

chore(deps): update dependency ts-loader to v9.6.2#64

Merged
victoraugustoas merged 1 commit into
mainfrom
renovate/ts-loader-9.x-lockfile
Jul 9, 2026
Merged

chore(deps): update dependency ts-loader to v9.6.2#64
victoraugustoas merged 1 commit into
mainfrom
renovate/ts-loader-9.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
ts-loader 9.6.09.6.2 age confidence

Release Notes

TypeStrong/ts-loader (ts-loader)

v9.6.2

Compare Source

Officially ts-loader has supported 3.6.3+ versions of TypeScript. This change means that certain scenarios with older versions of TS will now certainly fail. If anyone is actually using these versions it would be surprising.

v9.6.1

Compare Source


Configuration

📅 Schedule: (UTC)

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

@codecov

codecov Bot commented Jun 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate
renovate Bot force-pushed the renovate/ts-loader-9.x-lockfile branch from 2aeb7c5 to e5edc93 Compare July 6, 2026 12:12
@renovate renovate Bot changed the title chore(deps): update dependency ts-loader to v9.6.1 chore(deps): update dependency ts-loader to v9.6.2 Jul 6, 2026
@renovate
renovate Bot force-pushed the renovate/ts-loader-9.x-lockfile branch 6 times, most recently from 7c38b4d to 16d05c7 Compare July 9, 2026 20:20
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

Dependency Upgrade Analysis: no dependency changes detected in package.json for this PR.

@renovate
renovate Bot force-pushed the renovate/ts-loader-9.x-lockfile branch from 16d05c7 to 2fb22b4 Compare July 9, 2026 20:27
@github-actions

github-actions Bot commented Jul 9, 2026

Copy link
Copy Markdown

Dependency Upgrade Analysis

PR: #64 chore(deps): update dependency ts-loader to v9.6.2
Analyzed on: 2026-07-09 20:41 UTC
Triggered by: push to a dependency-update branch

Overall risk assessment

Package From To Risk Action
ts-loader 9.6.0 9.6.2 Low Proceed

ts-loader — 9.6.0 → 9.6.2

Section: devDependencies
Changelog: https://github.com/TypeStrong/ts-loader/blob/master/CHANGELOG.md
Releases: https://github.com/TypeStrong/ts-loader/releases/tag/v9.6.1, https://github.com/TypeStrong/ts-loader/releases/tag/v9.6.2

Summary

This is a lockfile-only bump — the declared range ^9.5.1 in package.json is unchanged and only the resolved version in pnpm-lock.yaml moves from 9.6.0 to 9.6.2. The intervening 9.6.1 ships a rspack compatibility fix; 9.6.2 is an internal cleanup that drops enhanced-resolve and semver at runtime and swaps micromatch for picomatch. No public API is removed, no options change. ts-loader is a webpack loader, and this project does not use webpack at build time, so the upgrade is effectively a passive dependency refresh.

Breaking changes

No breaking changes documented between 9.6.0 and 9.6.2. The release notes for 9.6.2 call out that ts-loader has historically supported TypeScript 3.6.3+ and that older TS scenarios are now more likely to fail outright, but this project pins typescript@^6.0.3 (package.json:64, resolved to 6.0.3 in pnpm-lock.yaml:125), well above the floor.

Deprecations

No new deprecations documented between 9.6.0 and 9.6.2.

Performance

No performance-impacting changes documented between 9.6.0 and 9.6.2. The dependency swap to picomatch is a neutral swap for a more actively maintained globby matcher; no measurable change is expected.

New APIs

None.

Configuration & environment

  • Node.jsengines.node is still >=12.0.0. .nvmrc pins 25.9.0, compatible.
  • Peer dependencies — unchanged: typescript: '*', webpack: ^4.0.0 || ^5.0.0, optional loader-utils: '*'. The lockfile shows the resolved pair ts-loader@9.6.2(typescript@6.0.3)(webpack@5.106.0) (pnpm-lock.yaml:7385).
  • TypeScriptts-loader officially supports >=3.6.3; project uses 6.0.3. Compatible.
  • Lockfilepnpm-lock.yaml already records the new resolved version (pnpm-lock.yaml:3399, snapshot at pnpm-lock.yaml:7385). No fresh pnpm install strictly required once the lockfile is committed; running pnpm install is the safest way to confirm the install graph still satisfies the existing package graph.

Project usage audit

  • Files referencing the package — 4 matches total, all in lockfile/manifest, none in source:
    • package.json:61 — declared range "ts-loader": "^9.5.1".
    • pnpm-lock.yaml:114 — dependency record under devDependencies.
    • pnpm-lock.yaml:3399 — package definition ts-loader@9.6.2.
    • pnpm-lock.yaml:7385 — snapshot ts-loader@9.6.2(typescript@6.0.3)(webpack@5.106.0).
  • APIs used — None. No file in src/, prisma/, or the repo root references ts-loader, nor is there a webpack.config.{js,ts} that consumes loader options.
  • Build / test pipelinesnest build (package.json:8) and jest (package.json:15, transforms via ts-jest, see jest.config.ts:8) — neither consumes ts-loader.
  • APIs NOT used — The whole loader surface (rule options, getCustomTransformers, appendTsSuffixTo, transpileOnly, etc.) is unused by this project. Removing the dependency entirely would also be safe, but is out of scope for this lockfile bump.

Migration plan

Trivial. The manifest range is already satisfied.

  1. Confirm the lockfile is in sync: pnpm install --frozen-lockfile.
  2. Sanity-build: pnpm build (runs nest build).
  3. Sanity-test: pnpm test (runs Jest via ts-jest).
  4. No source edits required — there are no ts-loader call sites or webpack configs to update.

Optional follow-up, outside this PR: if ts-loader is intentionally kept for future webpack support, document why in AGENTS.md; otherwise consider dropping it from devDependencies in a separate cleanup PR.


References

@renovate
renovate Bot force-pushed the renovate/ts-loader-9.x-lockfile branch from 2fb22b4 to d96dff0 Compare July 9, 2026 20:31
@renovate
renovate Bot force-pushed the renovate/ts-loader-9.x-lockfile branch from d96dff0 to 240cd4e Compare July 9, 2026 20:40
@victoraugustoas
victoraugustoas merged commit 00d3e42 into main Jul 9, 2026
4 checks passed
@victoraugustoas
victoraugustoas deleted the renovate/ts-loader-9.x-lockfile branch July 9, 2026 20:43
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