You must log in or register to comment.
This is a nice feature to add, but how do you use .env files effectively? They aren’t supposed to be checked in to Git. At runtime or on the CI you have better ways to set environment variables. I don’t understand the use case.
They are most useful during local development. It’s useful to have project-scoped config that your app interacts with in a manner identical to how it works in prod.
Generally you don’t commit to version control because you want to keep secrets out of there. However, it can be sometimes useful to hold non-sensitive config that you may want to commit but also to customize on prod. For instance like NODE_ENV, so you’re not building multiple mechanisms for configuring your code. But this is less useful and generally solved with a sample config that is copied to the .env file that is never pushed to VC.
