Native .env Support in Node.js: No More dotenv Required!

Managing environment variables is an essential part of modern app development. They help keep sensitive information like API keys, database credentials, and other configuration details secure and separate from your source code.

Until recently, most Node.js developers relied on libraries like dotenv to handle environment variables from a .env file. But now, with Node.js v20, you can access your environment variables without using any third-party packages. This new feature makes it easier, cleaner, and more secure to load environment variables in your Node.js applications.

In this blog, you’ll learn:

• What is native .env support?
• How to enable it in Node.js.
• Step-by-step instructions to set it up.
• Benefits of using native .env support over dotenv.

What is Native .env Support in Node.js?

Native .env support allows you to load environment variables directly from a .env file into your process.env object without the need for third-party libraries like dotenv.

This feature was introduced in Node.js v20, and it works by using the --env-file flag while running your Node.js application.

Before Node.js v20, you had to install dotenv and add this line to your application:

require('dotenv').config();

But now, with native support, you can skip the dotenv installation and just run your app like this:

node --env-file=.env app.js

That’s it! Node.js will automatically load the variables from the .env file and make them available via process.env.

How to Enable Native .env Support in Node.js

Step 1: Create a .env File

First, create a .env file in the root of your project (same directory as app.js).
Here’s an example .env file with a few environment variables:

PORT=3000
DB_HOST=localhost
DB_USER=root
DB_PASS=supersecretpassword

Important: Do not commit your .env file to version control (like GitHub) if it contains sensitive information. Use a .gitignore file to prevent it from being uploaded.

Step 2: Write Your Node.js Application

Next, create an app.js file in the same directory. This file will read and display the environment variables.

// Access environment variables using process.env
console.log('Server is running on port:', process.env.PORT);
console.log('Database Host:', process.env.DB_HOST);
console.log('Database User:', process.env.DB_USER);
console.log('Database Password:', process.env.DB_PASS);

Step 3: Run Your Node.js App

Now it’s time to run your app! Instead of using node app.js, you need to specify the .env file with the --env-file flag:

node --env-file=.env app.js

Output:

Server is running on port: 3000
Database Host: localhost
Database User: root
Database Password: supersecretpassword

As you can see, all environment variables from the .env file are now available in your app via process.env.

Benefits of Using Native .env Support

1. No More dotenv: There’s no need to install, configure, or maintain third-party packages like dotenv.
2. Simpler and Cleaner: No extra code is required in your application. You only use the --env-file flag.
3. Faster Start-Up: Since there’s no need to load additional libraries, your app might start slightly faster.
4. More Secure: Using fewer third-party libraries reduces security risks.

Comparison: Native .env vs dotenv

FAQs

1- Do I Need to Use dotenv in Node.js v20?

No! Native support makes dotenv unnecessary in most cases. Just use the --env-file flag when running your app.

2- Can I Use Multiple .env Files (like .env.development, .env.production)?

Unfortunately, native support for multiple .env files (like .env.production) is not as flexible as dotenv. You’ll need to specify the file explicitly:

node --env-file=.env.development app.js

3- What if I Don’t Want to Specify the –env-file Flag Every Time?

To avoid having to type --env-file=.env every time, you can use a package.json script.

"scripts": {
  "start": "node --env-file=.env app.js"
}

Then run it with:

npm start

Summary

• Node.js v20 and later offers native support for .env files.
• You no longer need to install dotenv.
• Just run your app like this:

node --env-file=.env app.js

This new feature simplifies the process of handling environment variables, reduces dependency bloat, and keeps your application fast and secure.

If you’re still using Node.js versions below v20, you’ll need to stick with dotenv. But as more developers upgrade to Node.js v20 and beyond, we’ll see less reliance on third-party packages.

Have you tried Node.js v20’s native .env support? Drop a comment below and let us know how it worked for you!