Your .env file is not yet read in when your JwtModule is instantiated. So either read it in earlier e.g. in your main.ts before the nest app is created or better: create a ConfigService and make the dependency on your config explicit: JwtModule.registerAsync({ imports: [ConfigModule], useFactory: async (configService: ConfigService) => ({ secret: configService.jwtSecret, }), inject: … Read more
I think the problem is related to webpack, I had the same problem on a next.js project and here is how I did to fix the problem. I created a next.conf.js file in my root folder where there is my .env file, I imported dotenv and I exported the module where there is all my … Read more
I had the same issue. Restarting VSCode solved the problem. See: https://github.com/motdotla/dotenv/issues/475 Edit: this seems to be an issue with the contents of dotenv’s package.json. There’s an open PR, but the author hasn’t replied/merged yet at this time. Link: https://github.com/motdotla/dotenv/pull/476 Edit 2: This should now be fixed! dotenv v8.4.0 fixes this issue. See https://github.com/motdotla/dotenv/releases/tag/v8.4.0.
It is more secure to store your secrets in a .env file than in the source code itself. But you can do one better. Here are the ways I’ve seen secrets managed, from least to most secure: Hard-code the secrets in the code. Pros: None. Don’t do this. Cons: Your developers will see your production … Read more
You should check if dotenv is installed, otherwise type in terminal: npm install –save dotenv or dotenv-extended npm install –save dotenv-extended
You could use string.replace with a regular expression as below to escape the \n characters again: “private_key”: process.env.GATSBY_GOOGLE_PRIVATE_KEY.replace(/\\n/g, ‘\n’),
Actually you have define the path of the .env file Try like this import * as dotenv from “dotenv”; dotenv.config({ path: __dirname+’/.env’ }); Try this also require(‘dotenv’).config({ path: __dirname+’/.env’ }); Change the path of .env file as required reference : https://github.com/motdotla/dotenv#options
From Nestjs docs here – https://docs.nestjs.com/techniques/configuration These steps worked for me with MySQL and TypeORM. Install Nestjs config module – npm i –save @nestjs/config. It relies on dotenv Create a .env file in your root folder and add your key/value pairs e.g. DATABASE_USER=myusername Open app.module.ts and import the config module import { ConfigModule } from … Read more
In 2022 both separate line comments and inline comments are supported. Line started with # symbol is a separate line comment. See the docs. Inlined # sign denotes the start of an inline comment (thanks to @reddisht to note this in comments). For vlucas/phpdotenv the same situation. Here is the example for both: # This … Read more