Stuck on an issue?
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.
Missing environment variables error is not as beautiful as before anymore
See original GitHub issueUsing alpha 2.0.0-alpha.880
Some errors such as when an environment variable is missing renders this error instead. The error was more beautiful before.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to add environment variables to AWS amplify?
The problem was that you can only set environment variables for apps connected to a GitHub repo. I was manually pushing, so the...
Read more >HTTP Client file not reading environment variables
I have added new variables before and it worked completely fine. I wanted to add a new variable "refreshToken", but since i changed...
Read more >Problems with Environment Variables
Environment variable is not set. If the error message states that the environment variable is not set, IT MEANS PRECISELY THAT ! The...
Read more >Environment variables not set anymore - Travis CI Community
Now they don't appear in the log anymore and “accidentally” our build is broken because of two missing env variables.
Read more >Using Environment Variables in Python for App Configuration ...
You may need to check if an environment variable exists, but don't necessarily care about its value. For example, your application can be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems that
prisma2 generatedoes not require environment variables anymore (which is the correct behaviour). So in theory, no, I can’t reproduce this.fixed in https://github.com/prisma/prisma-engines/commit/3ebc5fea01c4f428202f7a3c5703f6f64a904247