microsoft / microsoft/TypeScript
Support `diagnostics` inside `compilerOptions` in combination with `--build`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
- diagnostics, build
related maybe? https://github.com/microsoft/TypeScript/issues/19725
Suggestion
It would be nice if you could combine --diagnostics and --build
Use Cases
I can just cd into a specific sub-project and run tsc --diagnostics there without a problem, however it would be nice to also have --diagnostics for a whole monorepo / project-references build.
Examples
Checklist
My suggestion meets these guidelines:
- [*] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [*] This wouldn't change the runtime behavior of existing JavaScript code
- [*] This could be implemented without emitting different JS based on the types of the expressions
- [*] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- [*] This feature would agree with the rest of TypeScript's Design Goals.
Contributor guide
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 by reviewing related issue #19725 and comparing the existing tsc --diagnostics behavior with --build across project references. Locate the compiler option handling for diagnostics, compilerOptions, and --build, then define and test the expected diagnostics output for a whole monorepo build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100