can't pass --skipLibCheck at command line when using --build
#41185
Labels
Working as Intended
The behavior described is the intended behavior; this is not a bug
Comments
|
Please respect the issue templates for bug reports and feature requests. :-) This will make the work for the TypeScript team much easier and they can focus on improving the language, instead of deciphering GitHub issues. This is a duplicate of #25613. |
RyanCavanaugh
added
the
Working as Intended
|
👆 |
|
@RyanCavanaugh thanks, I'm aware of the due diligence expected when opening an issue. (I was an eclipse project lead for several years). I did try searching for |
MarcCelani-at
added a commit
to MarcCelani-at/TypeScript
that referenced
this issue
Sep 2, 2021
Summary: Many large composite projects rely on skipLibCheck to improve build times. However, skipLibCheck does introduce some risk that projects miss typescript errors in new node module versions they install. This is in response to Issues microsoft#45691, microsoft#25613, and microsoft#41185 Test Plan: New tsbuild unit test scenario that tests overriding the skipLibCheck value with a flag. Validated with verbose output that the actual build overrode the value in the tsconfig.json file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During development, my team uses a tsc watch task on a root tsconfig config that pulls in many other "project" tsconfigs. Only during a development/watch build, we would like all of these projects to be built with skipLibCheck
true, since it is ~5 times faster.The only way to do this seems to be to duplicate every tsconfig file (over 25 files), since the CLI doesn't support passing this option through to the references projects' tsconfigs.
The text was updated successfully, but these errors were encountered: