Fork TS Checker Webpack Plugin is a Webpack plugin that runs the TypeScript type checker in a separate process. It is useful for speeding up TypeScript type checking during builds and for reporting clearer TypeScript errors.
Project status
- This source appears to be in low-activity maintenance mode rather than actively evolving in 2026, since the last listed tagged updates are from 2025-04-03, even though the repo shows an upstream push on 2026-02-21.
- The apparent update cadence is irregular, with a long gap after 2025-04-03 (and no additional listed updates up to today, 2026-08-13).
AI summary generated
Recent updates
v9.1.0
v9.1.0 primarily changes the TypeScript error reporting output message to say "No typescript errors found." instead of the more generic "No errors found." The codebase also updates the project runtime requirement (Node engine) and upgrades chokidar, which can affect file watching behavior. Release notes only document the log message change.
BreakingFeaturesv9.0.3
Release v9.0.3 has essentially empty release notes, so documented changes cannot be confirmed. The code diff shows internal TypeScript worker configuration changes (notably removal of an enabled flag), plus major tooling and CI updates (Node and Yarn upgrades) and a large lockfile update.
Breakingv9.0.2
v9.0.2 primarily addresses an output formatting issue in `issue-webpack-error`, removing ANSI color codes from part of the webpack error message. In addition to that small code change, the release also bumps the `cosmiconfig` dependency and updates the lockfile substantially.
v9.0.1
v9.0.1 primarily addresses a case where the TypeScript compiler can crash during diagnostics collection, previously leaving the plugin without proper handling. In the diff, this is implemented by adding a try/catch around diagnostic retrieval and converting the crash into a synthetic TypeScript diagnostic.
v9.0.0
v9.0.0 is a tooling-focused release that removes Node.js v12 support, tightening the supported runtime range to Node.js >= 14. The code diff also shows multiple transitive dependency version bumps (via yarn.lock) and corresponding CI matrix adjustments, none of which are described in the release notes.
Breakingv8.0.0
Release v8.0.0 documents dropping support for Vue.js and a bug fix related to ignoring node_modules on Windows. However, the provided code diff shows multiple larger internal refactors (formatter handling, file change tracking, and ESLint reporter implementation) that are not mentioned in the release notes and could affect runtime behavior or configuration expectations.
Breakingv6.5.3
Release v6.5.3 is primarily described as a bug fix to make the performance API compatible with TypeScript 5. The code changes, however, also include additional watcher and file-change filtering behavior that is not mentioned in the release notes.
v7.3.0
v7.3.0 introduces a new `formatter.pathType` option to control whether issue file paths are formatted as `relative` (default) or `absolute`. The implementation adds a `pathType` concept throughout the formatter pipeline, including error construction and the webpack-like formatter.
Featuresv7.2.14
Release v7.2.14 has no substantive release note content beyond the version header. The actual diff shows changes limited to CI workflows, Husky hook commands, documentation, a test fixture dependency bump (TypeScript), and transitive dependency updates in yarn.lock.
v7.2.13
v7.2.13 focuses on performance by aborting stale type-check runs on fast recompilations. The code implements real cancellation for the issues worker and avoids logging expected abort-related errors.