: Use the hash symbol ( # ) to add comments or temporarily disable a variable.
"scripts": "dev": "next dev", // Uses .env.development "build:staging": "APP_ENV=staging next build", // Use custom env check "build:prod": "next build" // Uses .env.production
As developers, we often find ourselves juggling multiple projects simultaneously, each with its own set of dependencies, configurations, and environment variables. Managing these variables can become a daunting task, especially when working on different environments such as development, testing, and production. This is where .env.development comes into play – a simple yet powerful tool that simplifies the process of managing environment variables during development. .env.development
By understanding how to structure, load, and prioritize these files across different frameworks, and by adhering to security best practices, you ensure your application is robust, predictable, and ready for anything from a local development server to a global-scale production deployment. Remember the key takeaways: use the right file for the right job, never commit secrets, and always validate your variables. Your future self—and your fellow developers—will thank you.
For complex projects requiring more than three environments (development, staging, QA, etc.), many tools support custom environment files: : Use the hash symbol ( # )
The key takeaways are simple but impactful: use .env.development for team-shared development defaults, store secrets in .env.development.local and never commit them, always provide an .env.example template, properly configure your .gitignore to prevent leaks, and restart your server after making changes.
with spaces or special characters are wrapped in quotes ( "" or '' ). Comments can be added using the hash ( # ) symbol. The Environment File Hierarchy This is where
When a new developer clones the repository, they can copy the example file to create their own local configuration: cp .env.development.example .env.development Use code with caution. Keep Development and Production Credentials Isolated
.env.development is an environment-specific .env file designed exclusively for development use. It contains settings that help developers build and test features efficiently, typically including:
Because .env.development is typically committed to version control, all team members receive the same baseline development configuration when they clone the repository. New developers can get started immediately without manually configuring environment variables—the sensible defaults are already in place.
: Frameworks like React (via Create React App ), Next.js , and Vite automatically prioritize this file when you run commands like npm start or npm run dev . 2. Standard Preparation Steps