Open marktani opened 6 years ago
Yeah, that process should be more intelligent. Maybe using dotenv-save
.
For now, I'm using replaceInFiles(['.env], ...)
instead of writeEnv
and it fulfills my needs 🙂 So I'm not sure if we need to change the way writeEnv
works.
There's also a singular version replaceInFile
for single file replacement by the way...
Currently,
writeEnv
overwrites the file content of.env
. Anappend
option would be super useful to support existing.env
files.For example, in the node-advanced boilerplate, I use env var
APP_SECRET
that is gone after runningwriteEnv
.