Who 🤔 needs a middleman when you've got Express built-in?
Managing environment variables is a crucial aspect of ensuring your application runs consistently across different environments. Traditionally, developers have relied on the popular "dotenv" package from npm to load environment variables from a .env file into their Node.js applications. However, with the latest version of Express, there is now a built-in solution that makes environment variable management even simpler.

Understanding Environment Variables 🐬

Environment variables are key-value pairs that provide configuration settings for applications. They are typically used to store sensitive information such as API keys, database credentials, and other configuration details.

Why Use a .env File?

• Security: The primary reason is to protect sensitive information like API keys, database passwords, and secret tokens. By storing these values in a .env file, you prevent them from being accidentally committed to your code repository, reducing the risk of exposure.

• Configuration Management ⚙️: .env files are ideal for storing non-sensitive configuration settings that might vary between different environments (development, staging, production). This includes things like database URLs, API endpoints, and port numbers.

• Environment-Specific Values: You can use .env files to manage environment-specific variables that are not suitable for hardcoding in your code. This helps maintain code flexibility and adaptability.

What Kind of Variables to Store in a .env File?

Sensitive Information 👙:

• API keys (e.g., Stripe, Twilio, Google Maps,Rapid API)
• Database credentials (username, password, host, port, database name)
• Secret tokens (e.g., JWT secrets, encryption keys) OAuth credentials

Configuration Settings 🛠️:

• Base URLs for APIs
• File paths
• Port numbers
• Debug flags
• Environment-specific variables (e.g., development, staging, production)

How it used to be

Historically, developers relied on the dotenv package to manage environment variables in Node.js applications. However, with the introduction of the --env-file flag in Express, this dependency is no longer necessary.

"dotenv" was a popular package that allowed developers to load environment variables from a .env file into the Node.js process. This approach was convenient but introduced an additional dependency (i know a guy who knows a guy loop) .

How it's going

Modern versions of Express offer a built-in mechanism to load environment variables directly from a .env file. By using the --env-file flag when starting the Node.js process, you can bypass the need for dotenv altogether.
i.e
node --env-file .env index.js
also
nodemon --env-file .env index.js

This command instructs Node.js to load environment variables from the .env file located in the project's root directory.

Why Ditching dotenv is a Good Idea

• Reduced Dependencies
  Eliminating dotenv simplifies project setup and reduces potential conflicts.

• Simplified Configuration
  The process of loading environment variables becomes more streamlined.

• Improved Performance
  While the performance impact is likely minimal, removing unnecessary dependencies can potentially improve application startup time.

Remember: While .env files are helpful, it's essential to implement additional security measures, such as environment variable management tools and secure deployment practices, to protect sensitive information.

In real life there's a repo,vividly explaining this article,github repo