Deeply parse tsconfig
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 300
- Forks
- 30
- Avg merge
- 20h 45m
- Merged PRs (30d)
- 3
Description
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
- Would you be willing to help implement this feature?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the existing readTSConfig API and its handling of tsConfig.json. Review how TypeScript resolves extends and merges or replaces options such as baseUrl and paths. Done means a proposed parseTSConfig API can recursively resolve inherited configs and match TypeScript behavior for consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100