Update dependency ts-loader to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ts-loader	8.4.0 → 9.5.7

---

Release Notes

TypeStrong/ts-loader (ts-loader)

v9.5.7

Compare Source

• fix: TS5011 errors with TypeScript 6.0: transpileModule called with rootDir: undefined [#​1678] - thanks @​julioz and @​errorx666
• feat: migrate to trusted publishing - thanks @​johnnyreilly

Skipping 9.5.5-9.5.6 due to publishing issues

v9.5.4

Compare Source

• chore: typescript 5.9 upgrade - thanks @​johnnyreilly

Skipping 9.5.3 due to a publishing issue

v9.5.2

Compare Source

• fix: add more detailed error messages - thanks @​hai-x

v9.5.1

Compare Source

• fix: inputSourceMap can be null [#​1638] - thanks @​johnnyreilly and @​michaeltford

v9.5.0

Compare Source

• Feature: map the input source map in case ts-loader is used in a loader pipeline - thanks @​Ka0o0 and @​bojanv55

v9.4.4

Compare Source

• Bug fix: let users override skipLibCheck - thanks @​haakonflatval-cognite

v9.4.3

Compare Source

• Bug fix: add config file as build dependency - thanks @​alexander-akait

v9.4.2

Compare Source

• Bug fix: Use custom transformer when building solution references [#​1025] - thanks @​feosuna1

v9.4.1

Compare Source

• Hotfix: Disable enhanced-resolve - thanks @​manuth

v9.4.0

Compare Source

• Add Support for Resolving .cjs, .mjs, .cts and .mts Files [#​1503] - thanks @​manuth

v9.3.1

Compare Source

• Bug fix: Generate declaration files for js files if allowJs is set to true [#​1260] - thanks @​hediet and @​mvilliger

v9.3.0

Compare Source

• simplify configuration for fork-ts-checker-webpack-plugin - thanks @​piotr-oles

v9.2.9

Compare Source

• make v9 latest following v8 release - thanks @​johnnyreilly

v9.2.8

Compare Source

• Bug fix: support webpack 5 in ts-loader [#​1438] - thanks @​einatbar

v9.2.7

Compare Source

• cater for change in resolveTypeReferenceDirective API in TypeScript 4.7 [#​1421] - thanks @​johnny_reilly and @​cspotcode for inspiration in ts-node work here: TypeStrong/ts-node#1648

v9.2.6

Compare Source

• Docs fix for thread-loader / history - thanks @​johnnyreilly

v9.2.5

Compare Source

• Add function to get the latest program - thanks @​Zn4rK

v9.2.4

Compare Source

• Fix undefined configPath now falls back to default - thanks @​johnnyreilly

v9.2.3

Compare Source

• Fix error message for invalid getCustomTransformers modules - thanks @​blaky

v9.2.2

Compare Source

• Start consuming webpack loader types - thanks @​johnnyreilly
• Add webpack minimum version in peerDependencies - thanks @​afdev82

v9.2.1

Compare Source

• Make v9 latest in npm again - thanks @​johnnyreilly

v9.2.0

Compare Source

• Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @​timocov

v9.1.2

Compare Source

• Fix removed files handling in watch mode - thanks @​gasnier

v9.1.1

Compare Source

• update CHANGELOG.md for 8.2.0 release - thanks @​johnnyreilly

v9.1.0

Compare Source

• Use caches for module resolution and type reference directives when using compiler default functions - thanks @​sheetalkamat - uses: microsoft/TypeScript#43700

v9.0.2

Compare Source

• Remove usage of loader-utils - thanks @​jonwallsten

v9.0.1

Compare Source

• Use correct hook for emitting additional assets during compilation - thanks @​jonwallsten

v9.0.0

Compare Source

Breaking changes:

• minimum webpack version: 5
• minimum node version: 12

Changes:

• webpack 5 migration - thanks @​johnnyreilly, @​jonwallsten, @​sokra, @​appzuka, @​alexander-akait

---

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