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
Describe the feature
Currently the
readTSConfigonly parses the rawtsConfig.jsonfile, but a complete config may extend (extends) other config files. Some opitons, such asbaseUrl/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