useValue bugged in latest version

Bug Report

Current behavior

I try to write a dynamic module. Check the gist from 🙏 @evolkmann. I get a compiler error:

Returned expression type ... is not assigneable to DynamicModule

If you switch to useClass it seamlessly works. What am I doing wrong or is it a bug?

Input Code

https://gist.github.com/evolkmann/1019721d46304df3d8ff7adbca87d8ec

Expected behavior

No compiler error since this should work acc. to official docs and I assume gist worked once.

Possible Solution

It works with

{
 provide: MyLibService,
  useFactory: () => {
  return new MyLibService(type);
 },
}

But it should accept a value too…?

Environment

"@nestjs/common": "^6.7.2",
"@nestjs/core": "^6.7.2",
 
For Tooling issues:
- Node version:
"node": "10.16.2"
"npm": "6.10.3"
- Platform: Mac

Others:

[mambax]

🎺 Turns out, rm -rf .idea does not completely invalidate all caches, weird! I also deleted caches File > Invalidate caches / Restart and now it works. Sorry everyone to bother.

[kamilmysliwiec]

@angelov-todor @dboskovic just fixed in @nestjs/graphql@6.5.3. Thanks for reporting!