InjectModel brake on mongoose 5.12.9 and higher

[fasenderos]

Hi, I'm testing latest [email protected] with mongoose 5.12.9 (tested also with 5.12.10 and 5.12.12) but the InjectModel got breaked.

constructor(
  @InjectModel(Account)
  private readonly accountModel: ReturnModelType<typeof Account>
) {
    super(accountModel);
    console.log(accountModel); //  Model { undefined }    => typegoose beta.10+ and mongoose 5.12.9+
                                   Model { Account }      => typegoose beta.9 and mongoose 5.12.8
}

I have tried several combination of typegoose and mongoose and I can say that the maximum supported versions are typegoose beta.9 and mongoose 5.12.8. InjectModel stop working from mongoose 5.12.9 and higher.

To be noted that from typegoose beta.10 the minimum supported version of mongoose is 5.12.9 so I can't upgrade typegoose too.
Thanks in advance

[feliperoan]

Hello, could you solve it? I have the same error
Do you have a version that I can try in my package to solve the problem at least until there is a solution?

[fasenderos]

I did not found a solution, so I have to stay with typegoose beta.9 and mongoose 5.12.8

[OoDeLally]

I had a similar problem, and my mistake was a combination of various bad dependencies.
A - I was trying to export the model, instead of exporting the service.
or
B- I was exporting the service, but was including the service into the user's providers (which leads to a double-instantiation).
If you can create a minimal example, I can have a look, in case you made the same kind of mistakes.

[GuillaumeGSO]

Hi, i have a similar problem on a very simple training project.
@OoDeLally : fell free to have a look on this branch : https://github.com/GuillaumeGSO/notifications-project/tree/adding_mongodb

I've been stucked on this for hours now....
My model is NotificationData but the error keep using NotificationDataModel
@InjectModel(NotificationData)

Error: Nest can't resolve dependencies of the NotificationDataService (?). Please make sure
that the argument NotificationDataModel at index [0] is available in the AppModule context.

[OoDeLally]

@GuillaumeGSO You did the same mistake as I did:

@Module({
  imports: [
    TypegooseModule.forRoot(config.mongoURI), CompanyDataModule, NotificationsModule],
  controllers: [
    AppController, // Should be there since it is AppModule's responsibility to instantiate this.
    NotificationsController // Should NOT be here since it is NOT AppModule's responsibility to instantiate this.
  ],
  providers: [
    AppService,// Should be there since it is AppModule's responsibility to instantiate this.
    CompanyDataService, // Should NOT be here since it is NOT AppModule's responsibility to instantiate this. However since this one doesnt have any deps, it doesnt crash. It will be instantiated twice though.
    NotificationService,  // Should NOT be here since it is NOT AppModule's responsibility to instantiate this.
    NotificationDataService // Should NOT be here since it is NOT AppModule's responsibility to instantiate this.
  ],
})
export class AppModule {}

Including services and controllers into the controllers and providers will make Nest try to instantiate them from that module (here AppModule, which should not instantiate them, but merely import them from NotificationModule).
Only NotificationModule does have the required dependencies, and you only need to instanciate them from this module.

Remove the commented lines above, and your code will run.

[GuillaumeGSO]

Thank you so much !
Just few lines and you saved my day !