SequelizeModule.forRootAsync() dependency issue | NestJS | Page 1

wide geyser Jul 18, 2023, 1:05 PM

#

After adding the configuration module to better handle different environments for my application...

I get an error:

ERROR [ExceptionHandler] Nest can't resolve dependencies of the ProductRepository (?). Please make sure that the argument Sequelize at index [0] is available in the SequelizeModule context.

Potential solutions:
- Is SequelizeModule a valid NestJS module?
- If Sequelize is a provider, is it part of the current SequelizeModule?
- If Sequelize is exported from a separate @Module, is that module imported within SequelizeModule?
  @Module({
    imports: [ /* the Module containing Sequelize */ ]
  })

Here is my app module imports:

@Module({
  imports: [
    SequelizeModule.forRootAsync({
      imports: [ConfigModule],
      name: "pros_and_contractors",
      useFactory: (configService: ConfigService) => ({
        dialect: "postgres",
        host: configService.get<string>("database.host"),
        port: configService.get<number>("database.port"),
        username: configService.get<string>("database.username"),
        password: configService.get<string>("database.password"),
        database: configService.get<string>("database.database"),
        synchronize: true, // consider changing
        autoLoadModels: true, //consider changing
        models: [],
      }),
      inject: [ConfigService],
    }),
    ConfigModule.forRoot({
      envFilePath: ".env",
      isGlobal: true,
      load: [configuration],
    }),
    AuthModule,
    UserModule,
    ListingModule,
    ContractorModule,
    SupplierModule,
    ProductModule,
  ],
  controllers: [],
  providers: [],
})
export class AppModule {}

vivid path Jul 18, 2023, 1:08 PM

#

can youn run npx nest info

#

also, please don't use the NestJS Devtools tag unless your question is related with NestJS Devtools tool 🙂

wide geyser Jul 18, 2023, 1:10 PM

#

[System Information]
OS Version     : {REMOVED}
NodeJS Version : v16.15.1
NPM Version    : 8.19.2 

[Nest CLI]
Nest CLI Version : 9.2.0 

[Nest Platform Information]
platform-express version : 9.3.9
schematics version       : 9.0.4
sequelize version        : 9.0.0
passport version         : 9.0.3
swagger version          : 6.2.1
testing version          : 9.3.9
common version           : 9.3.9
config version           : 2.3.4
core version             : 9.3.9
jwt version              : 10.1.0
cli version              : 9.2.0

vivid path Jul 18, 2023, 1:10 PM

#

did you have Sequelize.forFeature somewhere?

wide geyser Jul 18, 2023, 1:11 PM

#

yes, in all the modules Im importing models into

#

for example

#


@Module({
  imports: [SequelizeModule.forFeature([Listing])],
  controllers: [ListingController],
  providers: [ListingService],
})
export class ListingModule {}

#

oh but not Sequelize.forFeature

#

that im not seeing anywhere at the moment

vivid path Jul 18, 2023, 1:13 PM

#

so you have that name in your forRoot but you didn't define the same connection name in the forFeature

#

I guess that's why

wide geyser Jul 18, 2023, 1:14 PM

#

I assume the name is the database name?

vivid path Jul 18, 2023, 1:14 PM

#

nop

#

the connection name

wide geyser Jul 18, 2023, 1:14 PM

#

oh so postgres?

vivid path Jul 18, 2023, 1:14 PM

#

as you have in SequelizeModule.forRootAsync(

#

see your code

#

wide geyser Jul 18, 2023, 1:15 PM

#

oh so I need to add name to this as well?

@Module({
  imports: [SequelizeModule.forFeature([Listing])],
  controllers: [ListingController],
  providers: [ListingService],
})
export class ListingModule {}

vivid path Jul 18, 2023, 1:15 PM

#

yes, unless you want to use the default connection name

wide geyser Jul 18, 2023, 1:15 PM

#

vivid path

yah that was added because I read it fixed some persons issue

#

ahh when I remove name, its unable to connect to database now

#

so it was right

vivid path Jul 18, 2023, 1:16 PM

#

feel free to try to improve the error message
it's quiet confusing

#

here's the source: https://github.com/nestjs/sequelize

GitHub

GitHub - nestjs/sequelize: Sequelize module for Nest framework (nod...

Sequelize module for Nest framework (node.js) 🍈. Contribute to nestjs/sequelize development by creating an account on GitHub.

wide geyser Jul 18, 2023, 1:17 PM

#

[Nest] 22287  - 18/07/2023, 16:16:13   ERROR [ExceptionHandler] Nest can't resolve dependencies of the ProductRepository (?). Please make sure that the argument Sequelize at index [0] is available in the SequelizeModule context.

Potential solutions:
- Is SequelizeModule a valid NestJS module?
- If Sequelize is a provider, is it part of the current SequelizeModule?
- If Sequelize is exported from a separate @Module, is that module imported within SequelizeModule?
  @Module({
    imports: [ /* the Module containing Sequelize */ ]
  })

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

Potential solutions:
- Is SequelizeModule a valid NestJS module?
- If Sequelize is a provider, is it part of the current SequelizeModule?
- If Sequelize is exported from a separate @Module, is that module imported within SequelizeModule?
  @Module({
    imports: [ /* the Module containing Sequelize */ ]
  })```

#

thats the full error, but I removed the error stack

#

because it has my computer info on it

wide geyser Jul 18, 2023, 1:18 PM

#

vivid path feel free to try to improve the error message it's quiet confusing

oh haha

#

dont have time for that right now

#

also im not sure what you mean by adding it to forFeatureit doesnt accept name

#

@vivid path reading through this, doesnt help either

#

https://docs.nestjs.com/techniques/database

Documentation | NestJS - A progressive Node.js framework

Nest is a framework for building efficient, scalable Node.js server-side applications. It uses progressive JavaScript, is built with TypeScript and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).

vivid path Jul 18, 2023, 1:26 PM

#

wide geyser also im not sure what you mean by adding it to `forFeature`it doesnt accept `nam...

pretty sure it does

#

read the TS docs

#

isn't in the docs site but you can find it out using the editor's intelisense
it's the second arg of forFeature()

#SequelizeModule.forRootAsync() dependency issue