NestJS does not recognize TypeORM .env configuration in production build

Question

NestJS does not recognize TypeORM .env configuration in production build

Currently, I am developing a NestJS application that interacts with a postgres database using TypeORM. During the development phase (npm run start:debug), everything functions perfectly. However, when I proceed to build the application with npm run build and attempt to run it via node /dist/main.js, I encounter an error preventing the application from starting:

error: password authentication failed for user "(my system user name)"
    at Parser.parseErrorMessage (/home/(my system user name)/application/node_modules/pg-protocol/dist/parser.js:287:98)

The implementation in my app.module file is quite basic:

import { Module } from '@nestjs/common';
import { TypeOrmModule } from '@nestjs/typeorm';
...
import { ConfigModule } from '@nestjs/config';

@Module({
    imports: [
        TypeOrmModule.forRoot(),
        ...
        ConfigModule.forRoot({
            isGlobal: true,
        }),
    ],
    controllers: [],
    providers: [],
})
export class AppModule {}

The TypeORM configuration details are stored in an .env file, which I also copy to the dist folder after building. Despite spending several days attempting to fix this issue, I have not been able to get it working properly in both development and production modes - even considering alternatives to utilizing an .env file as long as it ensures functionality across both environments. Any suggestions on why the configuration settings are not being recognized in production?

Edit: I have experimented with various other configuration methods as outlined in NestJS setup TypeOrm connection with .env and @nestjs/config, for instance. While some options showed promise during development, none were successful when deployed in a production build.

typescript environment-variables nestjs typeorm

Answer 1

Answer №1

The problem I encountered was not related to TypeORM or NestJS. It turned out that I inadvertently used a configuration hardwired in another part of the application. However, after some tweaking, I found that this Nest configuration suits my requirements perfectly:

import settings from './config/settings';
import { Module } from '@nestjs/common';
import { TypeOrmModule, TypeOrmModuleOptions } from '@nestjs/typeorm';
import { ConfigModule, ConfigService } from '@nestjs/config';

@Module({
    imports: [
        ConfigModule.forRoot({
            load: [settings],
            isGlobal: true,
        }),
        
        TypeOrmModule.forRootAsync({
            imports: [ConfigModule],
            inject: [ConfigService],
            useFactory: (configService: ConfigService) =>
                Object.assign({}, configService.get<TypeOrmModuleOptions>('database'), {
                    entities: [
                        (entity classes, auto-resolution does not work),
                        ...
                    ],
                })
        }),
        ...
    ],
    controllers: [],
    providers: [],
})
export class AppModule {}

Here is the relevant configuration file /config/settings.ts:

export default () => ({
    database: {
        type: ...,
        host: ...,
        port: ...,
        username: ...,
        password: ...,
        database: ...,
        synchronize: ...,
        logging: ...
    },
});

Answer 2

The problem I encountered was not related to TypeORM or NestJS. It turned out that I inadvertently used a configuration hardwired in another part of the application. However, after some tweaking, I found that this Nest configuration suits my requirements perfectly:

import settings from './config/settings';
import { Module } from '@nestjs/common';
import { TypeOrmModule, TypeOrmModuleOptions } from '@nestjs/typeorm';
import { ConfigModule, ConfigService } from '@nestjs/config';

@Module({
    imports: [
        ConfigModule.forRoot({
            load: [settings],
            isGlobal: true,
        }),
        
        TypeOrmModule.forRootAsync({
            imports: [ConfigModule],
            inject: [ConfigService],
            useFactory: (configService: ConfigService) =>
                Object.assign({}, configService.get<TypeOrmModuleOptions>('database'), {
                    entities: [
                        (entity classes, auto-resolution does not work),
                        ...
                    ],
                })
        }),
        ...
    ],
    controllers: [],
    providers: [],
})
export class AppModule {}

Here is the relevant configuration file /config/settings.ts:

export default () => ({
    database: {
        type: ...,
        host: ...,
        port: ...,
        username: ...,
        password: ...,
        database: ...,
        synchronize: ...,
        logging: ...
    },
});

NestJS does not recognize TypeORM .env configuration in production build

Answer №1

Similar questions

Will adding additional line breaks increase the overall length of the code?

Utilizing prerender.io with lazy loading in Angular 2: A comprehensive guide

Fix React/Typescript issue: Exported variable conflicts with name from external module

Decorators in Angular 4 using TypeScript are not permitted in this context

What is the best way to generate a dynamically interpolated string in JavaScript?

In a Typescript Next Js project, the useReducer Hook cannot be utilized

What is the proper way to utilize a class with conditional export within the Angular app.module?

angular2 with selenium webdriver: Issue with resolving 'child_process' conflict

The WebSocket connection in the browser, when accessed through a remote server, typically shows a CLOSED state in the readyState property during the on

What is the recommended way to handle data upon retrieval from a Trino database?

What is the best way to send an array of locationIds to the getLocationData service?

React JS displayed the string of /static/media/~ instead of rendering its markdown content

retrieve the initial subarray from the array using rxjs

Combine the object with TypeScript

Utilizing Global Variables and Passing Values in Ionic 3

Master Angular Autocompletion

Fastify Typescript: dealing with an unidentified body

What is the best way to update the image source in Angular 2?

Switch button - reveal/conceal details

The issue arises when using Angular Material as it seems that passing a data object to a matdialog dialog