· 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

  1. Cmd + Shift + P in your VSCode Editor
  2. Type “restart eslint server”
  3. It should appear as the first one and press “Enter”
  4. Issue resolved.

References

If you enjoyed this post, consider subscribing.
Get my next post delivered to you.

All articles