#My nest app didn't lauch properly since the switch to nest 9
5 messages · Page 1 of 1 (latest)
Suggestion for @fossil yoke:
Along with just manually verifying your dependencies are correct, as of Nest 8.1.0 you can set the NEST_DEBUG environment variable to a string that resolves as truthy, and get extra logging information while Nest is resolving all the dependencies for the application.
https://docs.nestjs.com/assets/injector_logs.png
The string in yellow is the host class of the dependency being injected, the string in blue is the name of the injected dependency, or its injection token, and the string in purple is the module in which the dependency is being searched for. Using this, you can usually trace back the dependency resolution for what's happening and why you're getting dependency injection problems.
Nest doest't seem to find the AuthModuleOptions, while I never us eir
It tries to resolve it in the code: ```ts
@Injectable()
export class OptionalAuthGuard extends AuthGuard('jwt') {
handleRequest(err, profile, info) {
return profile;
}
}
it's hard to tell what's going on without more code, I guess