Deeply parse tsconfig

Open kricsleo opened this issue 9 months ago • 0 comments

Describe the feature

Currently the readTSConfig only parses the raw tsConfig.json file, but a complete config may extend (extends) other config files. Some opitons, such as baseUrl/paths, will be merged/replaced. Could we propose a new API (e.g., parseTSConfig) to recursively resolve and merge configs to match TypeScript's behavior? This would allow other packages to utilize the full tsconfig.

Additional information

[x] Would you be willing to help implement this feature?

Mar 05 '25 03:03 kricsleo