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.
Add Support for More .env Files
See original GitHub issueProblem
I primarily use Prisma with Next.js, and since Next 9.4 they’ve implemented automatic .env detection, based on Create React App’s pattern: https://create-react-app.dev/docs/adding-custom-environment-variables/#what-other-env-files-can-be-used
When doing local development, my DATABASE_URL variable is kept in .env.local, which isn’t found by default when I run prisma generate so Prisma commands tend to require some overhead/repetition in my repo.
Suggested solution
Support for the additional .env files used by the popular JS meta frameworks.
Alternatives
A set of local development-specific Prisma commands using dotenv-cli
Issue Analytics
- State:
- Created 3 years ago
- Reactions:54
- Comments:6
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
Bump on this request
Yes! We also need this for Blitz. Here’s another issue for the same thing: https://github.com/prisma/prisma/issues/3720