NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #2380 most downloaded on npm
TypeScript loader for webpack
Last release 3 months ago
22 Jun 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
171 releases · first in 2015
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
One column per quarter.
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 @johnny_reilly 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
Fixed impossibility to have several instances of ts-loader with different compiler options - thanks @timocov
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 - thanks @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 CHANGEAdd a delay before starting the comparison tests to avoid failures under WSL - thanks @appzuka
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
Following the end of life of Node 8, ts-loader no longer supports Node 8 BREAKING CHANGE
ts-loader no longer supports Node 8 BREAKING CHANGEYour coding agent can read these notes before it upgrades. Set up the MCP server →