No information in stack trace about which dependency can't be resolved

I’m submitting a…

[ ] Regression 
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

I try to testing e2e using provided example in documentation, ( I have mongoose module also for database integration) but I got error, and can’t figure out, where I have mistake due to no detailed information about dependency which can’t be resolved.

 "before all" hook:
     Error: Nest can't resolve dependencies of the useFactory (?). Please verify whether [0] argument is available in the current context.
      at Injector.lookupComponentInExports (node_modules/@nestjs/core/injector/injector.js:129:19)

Expected behavior

Good to have detailed info in stack trace about which dependency can’t be resolved. (Angular provide detailed info about which dependency can’t be resolved)

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Nest version: 5.0.0

 
For Tooling issues:
- Node version: 10.1  
- Platform:  Mac 

Others:

[kamilmysliwiec]

In v5.0.1 you should receive a more descriptive error. Let me know if you still face any issue

[lock[bot]]

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.