Tell users they can bypass the compiler error
See original GitHub issue🚀 feature request
Relevant Package
Description
Users with the wrong TypeScript version get the error: ERROR in The Angular Compiler requires TypeScript >=3.6.4 and ❤️.7.0 but 3.7.2 was found instead.
When this error is hit, you should tell users they can bypass the error with:
"disableTypeScriptVersionCheck": true
Describe the solution you’d like
Tell people how to bypass it.
Describe alternatives you’ve considered
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Why do new programmers seem to ignore compiler error ...
The answer I'm looking for is not “they don't understand the error message”. That doesn't explain why they wouldn't consider telling anyone else ......
Read more >Ignore certain TypeScript compile errors? - Stack Overflow
So is there a way to tell it to ignore certain errors? I am sure given time there will be a nice way...
Read more >The compiler is unable to type-che… | Apple Developer Forums
Full error: The compiler is unable to type-check this expression in reasonable time; try breaking up the expression into distinct sub-expressions. I know...
Read more >Warning Options (Using the GNU Compiler Collection (GCC))
3.8 Options to Request or Suppress Warnings. Warnings are diagnostic messages that report constructions that are not inherently erroneous but that are risky ......
Read more >Compiler Warning (level 3) C4996 - Microsoft Learn
The compiler issues a deprecation warning for the original function name, and suggests the preferred name. To fix this issue, we usually ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Do we really want to do that (given that there are breaking changes in TS v3.7. that are not compatible with our code - e.g. the removal of
.typeArguments
)? 🤔It’s already documented in disabletypescriptversioncheck in aio.
I think, we don’t need anything more about this.
@kapunahelewong , could you please verify the above answer and kindly close this issue?