Closed alexander-ossur closed 6 years ago
remove noImplicitAny. This functionality is not currently available.
or you can set skipLibCheck
to true in tsconfig.
Thank you @wbhob,
skipLibCheck also did the trick. I think we will just put this into webpack.config.js, as long as our setup is complex (wallaby, mocha, and ton of others), and we want to be strict with our code as much as possible.
Meanwhile, is there any reason you won't plan to fix this? AFAIK it's pretty easy: function (args: any []): any
We may fix this in the next minor. @kamilmysliwiec if I PR can I get an express review and merge?
Hi @alexander-ossur, Thanks for reporting. @wbhob sure, feel free to create a PR 🙂
PR openned. Tests passing
@alexander-ossur it is very easy in concept, but all the internal code has to be refactored as well. I had to manually decide what type pretty much everything was in 170 different files.
Thank you guys. @wbhob Yes now, by seeing the changes made, I understand. Anyway thank you for your awesome work!
My pleasure!
Nest supports noImplicitAny now, as far as I know. This issue can be closed @kamilmysliwiec
I'm getting this error message after following the instructions here and running $ git clone https://github.com/nestjs/typescript-starter.git project
like it says
that repo is out of date. please use the cli or upgrade to nest v5
Ah ok. Thanks
@kamilmysliwiec do you want me to update the ts- and js-starter repos?
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
I'm submitting a...
Current behavior
Webpack + NestJS with help of ts-loader compiles with error
Once tsconfig.json is set to noImplicitAny: false it will compile just fine.
Expected behavior
It should not allow implicit "any" and compile with noImplicitAny: true without errors
Minimal reproduction of the problem with instructions
tsconfig.json
webpack.config.js
What is the motivation / use case for changing the behavior?
Environment