NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2380 most downloaded on npm
TypeScript loader for webpack
Latest stable
9.6.2
Last release 1 months ago
22 Oct 2026
Release timing varies
gaps range from 3 weeks to 1.2 years
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
172 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
Support TypeScript 7.1 API - thanks @johnnyreilly
This is a ground-up rewrite of ts-loader's compilation engine. Instead of driving TypeScript's classic LanguageService / Program / watch APIs, ts-loader now compiles exclusively through TypeScript's new native typescript/sync API (https://devblogs.microsoft.com/typescript/announcing-typescript-7-1-beta/#typescript-7.1-api) - the legacy compiler API integration has been removed entirely.
compiler option must now resolve to a package exposing a <compiler>/sync entry point (the TypeScript native API). Drop-in classic-API compilers (e.g. ttypescript) are no longer supported.compilerOptions loader option; the native API resolves a project's compiler options purely from its on-disk tsconfig.json, with no per-loader-instance override hook. Set compiler options in tsconfig.json instead.context loader option; the native API always resolves relative paths against the config file's own directory, with no basePath override exposed to let a tsconfig live outside the project root.happyPackMode loader option - HappyPack / thread-loader based parallelisation is no longer supported this way.experimentalFileCaching loader option; there's no equivalent under the native API's own caching model.experimentalWatchApi loader option, now that the native API supersedes TypeScript's classic watch API.onlyCompileBundledFiles loader option; the native API always resolves a project's own root files and offers no hook to restrict them to what webpack actually bundles.logInfoToStdOut. Set logInfoToStdOut: true to keep them on stdout.errorFormatter's colors argument is now a small picocolors-backed helper object instead of a chalk instance; chalk has been dropped as a runtime dependency in favour of picocolors.getCustomTransformers is still accepted for backwards compatibility but are now inert. The native API doesn't expose equivalent extension points for custom transformes. It is possible that the API will support these in future, and so the options have been left in place for now, but they will be removed if the API never exposes them.resolveModuleName and resolveTypeReferenceDirective are still accepted for backwards compatibility but are now inert. Support for custom resolvers is available: https://github.com/microsoft/TypeScript/pull/64299 - however it is not clear this is a feature generally used by ts-loader users and so has not been implemented at present.tsconfig.json are followed by the native API. The projectReferences loader option is accepted but has no effect, and v10 doesn't build referenced projects to disk the way tsc --build does.Your coding agent can read these notes before it upgrades. Set up the MCP server →
chore: trim runtime dependencies — remove enhanced-resolve/semver, swap micromatch → picomatch - thanks @johnnyreilly
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.
fix: rspack support - thanks @johnnyreilly and @bhollis
feat: add webpack 4 support back - thanks @johnnyreilly and @tweet
fix: TS5011 errors with TypeScript 6.0: transpileModule called with rootDir: undefined [#1678] - thanks @julioz and @errorx666
Skipping 9.5.5-9.5.6 due to publishing issues
chore: typescript 5.9 upgrade - thanks @johnnyreilly
Skipping 9.5.3 due to a publishing issue
fix: add more detailed error messages - thanks @hai-x
This release is actually v9.5.2 but due to a problem with the initial release workflow we incremented to v9.5.3
fix: inputSourceMap can be null [#1638] - thanks @johnnyreilly and @michaeltford
Feature: map the input source map in case ts-loader is used in a loader pipeline - thanks @Ka0o0 and @bojanv55
Bug fix: let users override skipLibCheck - thanks @haakonflatval-cognite
Bug fix: add config file as build dependency - thanks @alexander-akait
Bug fix: Use custom transformer when building solution references [#1025] - thanks @feosuna1
Hotfix: Disable `enhanced-resolve` - thanks @manuth
enhanced-resolve - thanks @manuthAdd Support for Resolving `.cjs`, `.mjs`, `.cts` and `.mts` Files [#1503] - thanks @manuth
.cjs, .mjs, .cts and .mts Files [#1503] - thanks @manuthBug fix: Generate declaration files for js files if allowJs is set to true [#1260] - thanks @hediet and @mvilliger
simplify configuration for fork-ts-checker-webpack-plugin - thanks @piotr-oles
make v9 latest following v8 release - thanks @johnnyreilly
Bug fix: support webpack 5 in ts-loader [#1438] - thanks @einatbar
cater for change in resolveTypeReferenceDirective API in TypeScript 4.7 [#1421] - thanks @johnnyreilly and @cspotcode for inspiration in ts-node work
Docs fix for thread-loader / history - thanks @johnnyreilly
Add function to get the latest program - thanks @Zn4rK
Fix undefined configPath now falls back to default - thanks @johnnyreilly
Fix error message for invalid getCustomTransformers modules - thanks @blaky
Start consuming webpack loader types - thanks @johnnyreilly
Make v9 latest in npm again - thanks @johnnyreilly
Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov
Fix removed files handling in watch mode - thanks @gasnier
update CHANGELOG.md for 8.2.0 release - thanks @johnnyreilly
Use caches for module resolution and type reference directives when using compiler default functions - thanks @sheetalkamat - uses: https://github.com
Remove usage of loader-utils - thanks @jonwallsten
Use correct hook for emitting additional assets during compilation - thanks @jonwallsten
webpack 5 migration - thanks @johnnyreilly, @jonwallsten, @sokra, @appzuka, @alexander-akait
Breaking changes:
Changes:
fix: cater for change in resolveTypeReferenceDirective API in 4.7 - thanks @dragomirtitian
v8.4.0
Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov* This is a backport from v9.2.0 for webpa
Use caches for module resolution and type reference directives when using compiler default functions - thanks @sheetalkamat - uses: https://github.com
feat: remove top-level typescript import statements - thanks @ulivz
Perf: Optimize fileExists callback path - thanks @berickson1
Included correct webpack source location in emitted errors - thanks @lorenzodallavecchia
Re-Fixed missing errors in watch mode in webpack5 - thanks @appzuka
Update definition files in watch mode in webpack@5 - thanks @appzuka,@JonWallsten,@alexander-akait
Upgrade `chalk`, `loader-utils`, and `semver` to latest stable versions - thanks Avi Vahl
Speed up builds by adding an in-memory cache to file path lookups - thanks @berickson1
Instead of checking date, check time thats more accurate to see if something has changed - thanks @sheetalkamat
Fixed build failing in yarn v2 pnp - @aicest
Fixed missing errors in watch mode in webpack5 - thanks @appzuka
Fixed build failing when using thread-loader - thanks @valerio
Fixed memory leak when using multiple webpack instances - thanks @valerio
Speeds up project reference build and doesnt store the result in memory - thanks @sheetalkamat
Fixed further deprecation warning on webpack@5 - thanks @appzuka
Fixed deprecation warnings on webpack@5 - thanks @sanex3339
Uses existing instance if config file is same as already built solution - thanks @sheetalkamat
Fix the wrong instance caching when using `appendTsSuffixTo` and `appendTsxSuffixTo` together - thanks @meowtec
Fix 2 issues with experimentalWatchApi - thanks @appzuka
Fix webpack deprecations - thanks @g-plane
ts-loader now supports TypeScript 3.6 and greater BREAKING CHANGE
ts-loader now supports TypeScript 3.6 and greater BREAKING CHANGEApply other loaders when updating files in watch mode - thanks @iorate
Ensure a separate webpack instance is created for different loader options - thanks @appzuka
Ensure that JSON files are included in build module resolution - thanks @berickson1
Make content hash consistent across machines - thanks @elyalvarado
* fix: watch-run - thanks @zn4rk
One column per quarter.