我正在尝试找到最合法的方式来建立使用.env文件的NestJS数据库。也就是说,我想使用@nestjs/config包来导入.env变量,并在TypeOrmModule中使用它们。
似乎我需要使用TypeOrmModule.forRootAsync。
我试着这样做:
// app.module.ts
@Module({
imports: [
ConfigModule.forRoot({
isGlobal: true,
}),
TypeOrmModule.forRootAsync({
useClass: TypeOrmConfigService,
}),
...
],
})
export class AppModule {}然后是TypeOrmConfigService
import { Module } from '@nestjs/common';
import { ConfigModule, ConfigService } from '@nestjs/config';
import { TypeOrmModuleOptions, TypeOrmOptionsFactory } from '@nestjs/typeorm';
@Module({
imports: [ConfigModule],
})
export class TypeOrmConfigService implements TypeOrmOptionsFactory {
constructor(private configService: ConfigService) {}
createTypeOrmOptions(): TypeOrmModuleOptions {
return {
type: 'mysql',
host: this.configService.get('DATABASE_HOST'),
username: this.configService.get('DATABASE_USERNAME'),
password: this.configService.get('DATABASE_PASSWORD'),
};
}
}最后一个是错误的:Nest can't resolve dependencies of the TypeOrmConfigService (?). Please make sure that the argument at index [0] is available in the TypeOrmCoreModule context.
如何修复它?或者(最好的)有没有NestJs + TypeOrm + @nestjs/config + .env (在存储库之外,使用DATABASE_PASSWORD) + config (我指的是处理config/development.yml、config/production.yml等的npm包配置)的例子?
似乎我在寻找一个非常标准的东西,hello world,它应该是每个NestJS项目的开始,但我发现很难将@nestjs/config和TypeOrm结合起来。
Upd。如果我用@Injectable替换@Module,错误是完全相同的:
yarn run v1.22.4
$ NODE_ENV=development nodemon
[nodemon] 1.19.0
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: /home/kasheftin/work/pubngn4/nestjs-course-task-management/src/**/*
[nodemon] starting `ts-node -r tsconfig-paths/register src/main.ts`
[Nest] 25384 - 09/01/2020, 8:07 PM [NestFactory] Starting Nest application...
[Nest] 25384 - 09/01/2020, 8:07 PM [InstanceLoader] AppModule dependencies initialized +11ms
[Nest] 25384 - 09/01/2020, 8:07 PM [InstanceLoader] TypeOrmModule dependencies initialized +0ms
[Nest] 25384 - 09/01/2020, 8:07 PM [InstanceLoader] PassportModule dependencies initialized +0ms
[Nest] 25384 - 09/01/2020, 8:07 PM [ExceptionHandler] Nest can't resolve dependencies of the TypeOrmConfigService (?). Please make sure that the argument at index [0] is available in the TypeOrmCoreModule context. +1ms
Error: Nest can't resolve dependencies of the TypeOrmConfigService (?). Please make sure that the argument at index [0] is available in the TypeOrmCoreModule context.
at Injector.lookupComponentInExports (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/injector.js:180:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at Injector.resolveComponentInstance (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/injector.js:143:33)
at resolveParam (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/injector.js:96:38)
at async Promise.all (index 0)
at Injector.resolveConstructorParams (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/injector.js:112:27)
at Injector.loadInstance (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/injector.js:78:9)
at Injector.loadProvider (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/injector.js:35:9)
at async Promise.all (index 3)
at InstanceLoader.createInstancesOfProviders (/home/kasheftin/work/pubngn4/nestjs-course-task-management/node_modules/@nestjs/core/injector/instance-loader.js:41:9)
1: 0xa2afd0 node::Abort() [/home/kasheftin/.nvm/versions/node/v14.3.0/bin/node]
2: 0xa9e7a9 [/home/kasheftin/.nvm/versions/node/v14.3.0/bin/node]
3: 0xc06bab [/home/kasheftin/.nvm/versions/node/v14.3.0/bin/node]
4: 0xc08156 [/home/kasheftin/.nvm/versions/node/v14.3.0/bin/node]
5: 0xc087d6 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/home/kasheftin/.nvm/versions/node/v14.3.0/bin/node]
6: 0x13a9f19 [/home/kasheftin/.nvm/versions/node/v14.3.0/bin/node]
Aborted (core dumped)
[nodemon] app crashed - waiting for file changes before starting...发布于 2020-09-14 15:04:11
这是我在app.module.ts中使用Postgres的工作脚本,但对于MySQL将非常相似。有时在重建之前需要手动删除dist文件夹-当数据库无法同步时。
import { ConfigModule, ConfigService } from '@nestjs/config';
@Module({
imports: [
ConfigModule.forRoot(),
TypeOrmModule.forRootAsync({
imports: [ConfigModule],
useFactory: (configService: ConfigService) => ({
type: 'postgres' as 'postgres',
host: configService.get<string>('DATABASE_HOST'),
port: parseInt(configService.get<string>('DATABASE_PORT')),
username: configService.get<string>('DATABASE_USER'),
password: configService.get<string>('DATABASE_PASS'),
database: configService.get<string>('DATABASE_NAME'),
entities: [__dirname + '/**/*.entity{.ts,.js}'],
synchronize: true,
}),
inject: [ConfigService],
}),根文件夹中的.env
DATABASE_USER=
DATABASE_PASS=
DATABASE_HOST=
DATABASE_NAME=
DATABASE_PORT=发布于 2020-10-04 19:06:36
不确定它是否仍然相关,然而,我认为这就是正在发生的事情。
你看到的错误"Nest cant't resolve...“意味着您正在尝试使用依赖注入注入一个类,但是Nest在依赖容器中找不到这个依赖。
为了解决此问题,您需要将ConfigService (无法解析依赖项)添加到app.module.ts提供程序部分。
大概是这样的:
@Module({
imports: [
ConfigModule.forRoot(),
TypeOrmModule.forRoot({
type: 'mysql',
host: process.env.DATABASE_HOST,
username: process.env.DATABASE_USERNAME,
password: process.env.DATABASE_PASSWORD,
}),
...
],
providers: [
ConfigService
]
})
export class AppModule {}发布于 2021-01-11 11:32:24
你可以使用"nestjs-easyconfig",我将其用于多个配置(例如:.env.development,.env.production‘它几乎与.env /.env.production相同。你可以查看我的github repo
https://stackoverflow.com/questions/63678216
复制相似问题