chore(deps): update dependency ts-loader to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ts-loader	7.0.0 -> 9.5.4

---

Release Notes

TypeStrong/ts-loader (ts-loader)

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

v8.4.0

Compare Source

• fix: cater for change in resolveTypeReferenceDirective API in 4.7 - thanks @​dragomirtitian
• This is a backport from v9.2.7 for webpack 4 compatibility

v8.3.0

Compare Source

• Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @​timocov
• This is a backport from v9.2.0 for webpack 4 compatibility

v8.2.0

Compare Source

• Use caches for module resolution and type reference directives when using compiler default functions - thanks @​sheetalkamat - uses: microsoft/TypeScript#43700
• This is a backport from v9.1.0 for webpack 4 compatibility

v8.1.0

Compare Source

• feat: remove top-level typescript import statements - thanks @​ulivz

v8.0.18

Compare Source

• Perf: Optimize fileExists callback path - thanks @​berickson1

v8.0.17

Compare Source

• Included correct webpack source location in emitted errors - thanks @​lorenzodallavecchia

v8.0.16

Compare Source

• Re-Fixed missing errors in watch mode in webpack5 - thanks @​appzuka

v8.0.15

Compare Source

• Update definition files in watch mode in webpack@5 - thanks @​appzuka,@​JonWallsten,@​alexander-akait
• Add afterDeclarations to getCustomTransformers in README.md - thanks @​appzuka

v8.0.14

Compare Source

• Upgrade chalk, loader-utils, and semver to latest stable versions - thanks Avi Vahl

v8.0.13

Compare Source

• Speed up builds by adding an in-memory cache to file path lookups - thanks @​berickson1

v8.0.12

Compare Source

• Instead of checking date, check time thats more accurate to see if something has changed - thanks @​sheetalkamat

v8.0.11

Compare Source

• Fixed build failing in yarn v2 pnp - thanks @​aicest

v8.0.10

Compare Source

• Fixed missing errors in watch mode in webpack5 - thanks @​appzuka

v8.0.9

Compare Source

• Fixed build failing when using thread-loader - thanks @​valerio

v8.0.8

Compare Source

• Fixed memory leak when using multiple webpack instances - thanks @​valerio

v8.0.7

Compare Source

• Speeds up project reference build and doesnt store the result in memory - thanks @​sheetalkamat

v8.0.6

Compare Source

• Fixed further deprecation warning on webpack@5 - thanks @​appzuka

v8.0.5

Compare Source

• Fixed deprecation warnings on webpack@5 - thanks @​sanex3339

v8.0.4

Compare Source

• Uses existing instance if config file is same as already built solution - thanks @​sheetalkamat

v8.0.3

Compare Source

• Fix the wrong instance caching when using appendTsSuffixTo and appendTsxSuffixTo together - thanks @​meowtec

v8.0.2

Compare Source

• Fix 2 issues with experimentalWatchApi - thanks @​appzuka

v8.0.1

Compare Source

• Perf: Optimize fileExists callback path - thanks @​berickson1

v8.0.0

Compare Source

• Support for symlinks in project references - thanks @​sheetalkamat!
• ts-loader now supports TypeScript 3.6 and greater BREAKING CHANGE

v7.0.5

Compare Source

• Add a delay before starting the comparison tests to avoid failures under WSL - thanks @​appzuka
• Apply other loaders when updating files in watch mode - thanks @​iorate

v7.0.4

Compare Source

• Ensure a separate webpack instance is created for different loader options - thanks @​appzuka

v7.0.3

Compare Source

• Ensure that JSON files are included in build module resolution - thanks @​berickson1

v7.0.2

Compare Source

• Make content hash consistent across machines - thanks @​elyalvarado

v7.0.1

Compare Source

• fix: watch-run - thanks @​zn4rk

---

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

[renovate]

⚠ Artifact update problem

Renovate failed to update artifacts 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: packages/guess-webpack/package-lock.json

npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: guess-webpack@0.4.22 npm ERR! Found: webpack@4.47.0 npm ERR! node_modules/webpack npm ERR! webpack@"^4.14.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer webpack@"^5.0.0" from ts-loader@9.5.1 npm ERR! node_modules/ts-loader npm ERR! dev ts-loader@"9.5.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /tmp/worker/0b0934/069144/cache/others/npm/_logs/2023-11-15T04_59_44_487Z-eresolve-report.txt npm ERR! A complete log of this run can be found in: /tmp/worker/0b0934/069144/cache/others/npm/_logs/2023-11-15T04_59_44_487Z-debug-0.log 

File name: package-lock.json

npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: guess@0.0.0 npm ERR! Found: webpack@4.46.0 npm ERR! node_modules/webpack npm ERR! dev webpack@"4.46.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer webpack@"^5.0.0" from ts-loader@9.5.1 npm ERR! node_modules/ts-loader npm ERR! dev ts-loader@"9.5.1" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! npm ERR! For a full report see: npm ERR! /tmp/worker/0b0934/069144/cache/others/npm/_logs/2023-11-15T05_00_24_650Z-eresolve-report.txt npm ERR! A complete log of this run can be found in: /tmp/worker/0b0934/069144/cache/others/npm/_logs/2023-11-15T05_00_24_650Z-debug-0.log