2 ms·
Yes, although the same can be said for the "no implicit any" flag when migrating from code bases EcmaScript. They seem to be doing a pretty good job of support
by klodolph 10y ago
Yes, although the same can be said for the "no implicit any" flag when migrating from code bases EcmaScript. They seem to be doing a pretty good job of supporting both legacy and greenfield projects.
- k__ 10y agoYes, I tried "no implicit any" and got nothing working. Problem were mainly 3rd party libs with out-dated, bad or no type definitions. Is it even possible to use these flags with production code?
- RyanCavanaugh 10y agoWe've removed nearly all the implicit anys from DefinitelyTyped, so if you're getting definitions from there, you shouldn't see any. We don't have good data on this but my perception from talking to people on GitHub is that the vast majority of people using TypeScript run with 'no implicit any' on once they get their codebases converted. (I'm on the TypeScript team)
- k__ 10y agoNice to read :) Had some problems with React/JSX back in the days.
- johnny_reilly 10y agoAnd even if noImplicitAny in 3rd party libraries is not honoured you now have: skipLibCheck which will limit checks to your own code. Details here: https://www.typescriptlang.org/docs/handbook/compiler-options.html https://www.typescriptlang.org/docs/handbook/compiler-option... I believe it's actually a perf gain to run with this set (but I'm not certain).