Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
.env variables behave different between local and Vercel
See original GitHub issueBug report
Describe the bug
Environment variables cannot be accessed in api routes when deployed on Vercel using the latest 9.4 environment variable feature.
However, when running next locally, then they do have access to the environment variables.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
See minimal reproduction sample: https://github.com/TheHolyWaffle/env-test
- Create .env file with “TEST=Hello World”
- Create an api route that echoes that env variable
- Deploy to Vercel
Expected behavior
The deployment on Vercel should have the same .env behaviour as when running nextjs locally using next dev.
- Local: the api route correctly echoes “Hello World”.
- Vercel: the api route returns an internal server error. (Try https://env-test.theholywaffle.now.sh/api/print)
System information
- Next.js 9.4.2
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Can confirm that 9.4.3-canary.1 seems to have fixed the issue: https://env-test-three.now.sh/api/print
I’ll try. Thanks!