How do I debug dotenv issues?
Enable debug mode: require('dotenv').config({ debug: true }). This logs every variable that dotenv loads, the file path it's reading from, and any parsing issues. Also check console.log(process.env) to see all loaded variables (be careful not to log secrets in production).
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in dotenv Troubleshooting Common Issues Undefined Variables and Loading Problems
Common causes: dotenv not loaded (add require('dotenv').config() at the top), variable not in .env file, typo in variable name, or .env file not in the right location (dotenv looks in process.cwd()). Use debug: true to see what dotenv is loading.
dotenv must be loaded before any module that uses process.env. If a config module is imported before require('dotenv').config(), the variables will be undefined. Load dotenv at the very top of your entry file (server.js or app.js).
Use quotes: JWT_SECRET="my secret with spaces". For multi-line values (like private keys), use double quotes. For values with # (which dotenv interprets as comments), wrap in quotes: API_KEY="abc#123".
Still have questions?
Browse all our FAQs or reach out to our support team