· 1 min read
#026
NestJS Linting Error - Unsafe call of a type that could not be resolved
nestjs backend
I came back exploring a NestJS framework recently and bootstrap a new NestJS project.
I encountered an Typescript ESLint error like the one below:
Unsafe call of a type that could not be resolved.
I am thinking to myself how come a new NestJS project could have so many linting errors, and turned out it was just glitch.
I found a working solution on Reddit and it is simple - just restart your ESLint Server.
Below are the steps by steps guide for workaround:
Steps
- Cmd + Shift + P in your VSCode Editor
- Type “restart eslint server”
- It should appear as the first one and press “Enter”
- Issue resolved.
References
- Reddit thread