Transcript from the "Making Anys Explicit" Lesson
>> Mike North: Step 2, you will start with your tests passing, you will ban implicit anys. And this is a tsconfig compiler option, noImplicitAny, true. So setting that to true means, instead of TypeScript falling back to any in places where it can't figure things out through inference, it will throw an error at you.
[00:00:26] Not throw an error but it will give you a compile error.
>> Mike North: So you're gonna then have basically a to-do list, and it's mostly going to consist of implicit anys that now have turned into compile errors. And you are gonna go through and provide meaningful types where you can, and where you can't, you'll use an explicit any.
[00:01:43] DefinitelyTyped publishes out to thousands of libraries and they all are in the npm package scope at typed or at types. So you'll see at types slash lodash. And if you look in the package JSON on this workshop project, I think you'll see at types slash node. So that has the fs module and the path module, all the type information there, right?
[00:02:11] So this is a good time to sort of start bringing that in as a way of combating these implicit anys. And then you're going to get your test passing again, and this is a second independent poll request.