如何将 nodemon 与 .env 文件一起使用？

Question

I am using an.env file to hold environment variables for the server. This works if I run the server with foreman start. But it doesn't work with nodemon.

I would like to use nodemon instead because it restarts automatically when you modify the server. How can I get nodemon to work with.env files?

Answer 1

I have a production Procfile with:

web: node web.js

So I have created a Procfile_dev file with:

web: nodemon web.js

And when I am at development environment I run:

$ foreman start -f Procfile_dev

It works like a charm and doesn't affect production.

Answer 2

1. Install dotenv npm i dotenv
2. Create .env file and your variables inside

3. Add the script to execute

   "dev": "nodemon -r dotenv/config ./app/index.js " or "start": "node -r dotenv/config ./app/index.js "

4. Run the app using npm run dev or npm run start

Answer 3

You can get nodemon to directly use the .env with the following command

$: env $(cat .env) nodemon app.js

Be aware that you'll have to restart it if you make changes to .env and it won't like it if there are any spaces in your .env file.

Answer 4

With recent versions of Node (since io.js 1.6), you can pass it the -r flag to require a module on start. This lets you directly load .env by using nodemon's --exec :

nodemon --exec 'node -r dotenv/config'

This requires the npm package dotenv to be installed.

Answer 5

将您的本地配置变量放在 .env 文件中，并使用以下命令运行 foreman 和 nodemon

$ foreman run nodemon web.js

Answer 6

This works pretty well for me so far,

nodemon  -w . -w .env index.js

How it works:
" -w . " tells nodemon to watch the files in the current directory
" -w .env " tells nodemon to watch the .env file
" index.js " is just the file to run when changes occur (could be anything)

Answer 7

"scripts": {
    "start": "node -r dotenv/config src/server.js dotenv_config_path=dev.env dotenv_config_debug=true",
    "start:dev": "nodemon --exec \"npm start\""
  }

Answer 8

In my case the .env file is used for development and not deployment. So I wanted my code to be decoupled from the .env file. Ideally I didn't want to import 'dotenv/config' anywhere in my code. This is my solution:

My nodemon config:

{
  "watch": [
    "src",
    ".env"
  ],
  "ext": ".ts",
  "exec": "ts-node -r dotenv/config ./src/index.ts"
}

My NPM script:

"start:dev": "nodemon"

In this solution ts-node requires dotenv, which sets up the environment variables before the main app starts. This means that nowhere in my code do I need a import 'dotenv/config' . dotenv can become a dev dependency, and this also prevents dotenv to be loaded at all once the code is deployed.

Answer 9

Thread necromancy!

Use grunt-env to load environmental variables from your heroku config.

Answer 10

In Three steps

1. Creating the file on root folder > .env

# .env ======
PORT=5000
WHO_AM_I="Who Knows"

2. Install the dotenv
3. Run below command

"dev": "nodemon -r dotenv/config src/app.js"

You can access the your defined variables using > process.env.varible_name

Answer 11

Use the -w key to specify nodemon what to watch additionally.

"scripts": {
    "dev": "env-cmd nodemon -w app -w *.js -w .env server.js"
}

Don't forget rerun npm run dev

Answer 12

If you want to run Typescript in nodemon and require a particular .env file with dotenv then you can do:

In package.json scripts:

"dev": "nodemon -r dotenv/config src/myApp.ts dotenv_config_path=/path/to/your/env/file",

And a line in nodemon.json to tell nodemon to use ts-node when encountering Typescript extensions:

"execMap": {"ts": "node -r ts-node/register"},

This is useful for using a development .env file say .env.development.local for local dev work and leave the main .env file for live production variables.

Answer 13

Heroku Procfile

Change: web: node app.js to web: nodemon app.js

Answer 14

要将 dotenv 包和任何声明的 .env 变量加载到环境中，您可以执行以下操作：

nodemon -r dotenv/config myapp.js

Answer 15

I use cross-env for environments.

npm i cross-env

set package.json .

"start": "cross-env NODE_ENV=production node dist/app.js",
"dev": "cross-env NODE_ENV=dev nodemon --exec ts-node src/app.ts",

npm run start OR npm run dev