get-tsconfig is a lightweight TypeScript utility that finds and parses tsconfig.json files, including handling comments, dangling commas, and resolving the extends chain. It can also validate whether a found tsconfig applies to a specific file and provides typed, resolved tsconfig output plus helpers for matching include/exclude/files and compilerOptions.paths.
Project status
- Actively maintained, with very recent GitHub activity (last upstream push 2026-04-30) and multiple tagged
v5.0.0-beta.*updates through April 2026. - Update cadence looks brisk for the
v5line, about every 2 to 6 weeks across early 2026 (for example, beta.1 on 2026-02-06, beta.2 on 2026-03-19, beta.4 on 2026-04-15, beta.5 on 2026-04-30).
AI summary generated
Recent updates
v5.0.0-beta.5
v5.0.0-beta.5 introduces TypeScript-version-aware compiler option defaults that are applied by default when calling `readTsconfig` and `getTsconfig`. The implementation auto-detects the installed TypeScript major version and then injects unconditional compiler-option defaults that TypeScript itself would synthesize at runtime.
BreakingFeaturesv5.0.0-beta.4
This release focuses on tsconfig parsing and extends-chain handling, including fixes around how `files` and `include` interact and improved rewriting of inherited path fields. The documented surface area includes an `includes` option for `getTsconfig` and `findTsconfig`, plus a new `findTsconfig` export and a `PathsMatcher` type export.
Featuresv4.14.0
v4.14.0 adds a new `findTsconfig` API and introduces an `includes` option to both `getTsconfig` and `findTsconfig`. When `includes` is enabled, the implementation validates that the discovered tsconfig actually applies to the provided search path (via `files`, `include`, and `exclude`).
Featuresv4.13.8
v4.13.8 ships a fix in parse-tsconfig focused on how inherited compilerOptions path fields are rewritten when using tsconfig extends. The code changes also adjust include/files handling and normalize some relative path values, with new tests covering these cases.
v5.0.0-beta.3
v5.0.0-beta.3 includes a bug fix related to how `files` and `include` are combined in tsconfig matching, and a package-level change to improve tree-shaking. The code diff, however, shows a much larger refactor of the public API and core entrypoints than what the release notes document.
v4.13.7
v4.13.7 contains a targeted bug fix in parse-tsconfig. It changes how the library handles tsconfig objects that specify both `include` and `files`, ensuring `files` is not dropped.
v5.0.0-beta.2
v5.0.0-beta.2 is a major API refactor that reworks tsconfig reading and resolution around a new readTsconfig/getExtendsChain/resolveExtendsChain pipeline, and replaces the old path/files matcher APIs with simpler functions (resolvePathAlias, isFileIncluded). It also introduces an includes option for tsconfig discovery and shifts the package to ESM only, along with broad type renames and option-object signatures.
BreakingFeaturesv5.0.0-beta.1
v5.0.0-beta.1 primarily updates Node.js support, dropping Node.js versions below 20. The release notes only call out the Node minimum version change, but the code diff also shows build target and CI workflow behavior changes, plus an additional test covering tsconfig extends include path inheritance from subdirectories.
Breakingv4.13.6
v4.13.6 updates parse-tsconfig behavior around how it populates tsconfig.exclude. The release notes describe a bug fix that prevents outDir from being automatically added to exclude when exclude is explicitly provided.
v4.13.5
v4.13.5 includes a single bug fix in the `paths-matcher` logic. It restores TypeScript-like behavior where, if no `paths` pattern matches, module specifiers fall back to resolving via `baseUrl`.