Type check command
See original GitHub issueDescription
One way I leverage TypeScript is when making a behavioral change to my project is to ensure the source of the change is a compilation mistake.
Being able to run a type check over the entire project through VS Code and use the TypeScript problem matcher to ensure they are surfaced in the Problems
tab
Motivation
Being able to surface all build errors in a repo is very handy, especially when making a change to one to the shared projects.
Suggested Implementation
Until the solution file exists, running tsc -p apps/*/tsconfig.json --noEmit --incremental
for each app tsconfig?
Alternate Implementations
Maintain a solution tsconfig.all.json, I read there were some issues with having one so having it named differently should stop it being picked up by VSCode. I think we would then need tsconfig.check.json
for each project which sets no-emit and incremental.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:35
- Comments:40 (10 by maintainers)
@JakeGinnivan Again - thank you 👍
For anybody interested: this is a repo with working command
tsCheck
- https://github.com/petrkrejcik/nx-test Steps to add it to your monorepo:tools/executors/tsCheck
workspace.json
to all desired projects:nx run <appName>:tsCheck
@JakeGinnivan that looks nice but I am not sure if the solution is to not use nrwl’s app plugins. 😅 Although I totally understand that this may take months to be resolved…
I know this is open source and everything but do people really use in production something that doesn’t tell them typescript errors by default? We can always write our own solution but that kind of kills the point of “standardization”. 🙂 I focus on code quality and this is a major blocker for me.
Every project should have:
otherwise it should never make it to production. 🙉