STRIPE_PUBLIC_KEY=pk_test_your_key_here FIREBASE_API_KEY=your_dev_firebase_key Use code with caution. Copied to clipboard Framework-Specific Naming Rules Most modern frameworks require a specific
The Definitive Guide to .env.development in Modern Web Development
: Top priority. Overrides everything. Used for machine-specific overrides that individual developers need but should never share with teammates.
.env .env.local .env.development.local .env.production .env.production.local Use code with caution. Utilize a .env.example Template .env.development
However, hardcoding localhost in production would be catastrophic. This is where environment-specific files shine.
Stop the server ( Ctrl+C ) and restart it. For Next.js, you may need to run next clean to clear the cache.
Sensitive production keys should never touch your local machine's configuration files. Keeping local mock keys in .env.development ensures that even if you accidentally share a screenshot of your local config, your "real" secrets remain safe. Best Practices for Setup This is where environment-specific files shine
: Share a standard set of non-sensitive development variables with your team via a template (often called .env.example ). Common Use Cases
Mastering .env.development is an essential skill for any modern web developer. It transforms environment management from a source of fragile bugs and configuration errors into a structured, secure, and efficient workflow.
In a standard Node.js application, the dotenv package does not automatically look for .env.development . You must explicitly configure it using the dotenv-flow package or by conditionally loading the file based on process.env.NODE_ENV . javascript console.log(`Server listening on port $process.env.PORT`)
# .env.development.example DATABASE_URL="Your local database connection string here" STRIPE_API_KEY="Your Stripe test API key" ENABLE_NEW_DASHBOARD=false Use code with caution.
app.listen(process.env.PORT, () => console.log(`Server listening on port $process.env.PORT`); );