@dotenvx/dotenvx
Advanced tools
Changelog
1.21.0
🎓 now if you choose to single quote, double quote, no quote, or backtick your value it will be respected - including for encrypted values. this more intuitively handles complex cases like escaped characters, literals, and json.
Changelog
1.20.0
process.env.DOTENV_PRIVATE_KEY
and/or process.env.DOTENV_PUBLIC_KEY
on set
(#401)process.env.DOTENV_PRIVATE_KEY
and/or process.env.DOTENV_PUBLIC_KEY
on encrypt
(#411)process.env.DOTENV_PRIVATE_KEY
on decrypt
(#412)logger.help
to use brighter blue (#414)main.decrypt,encrypt,set
(#410)Changelog
1.18.0
set
and encrypt
preserve leading spaces (#395) HELLO=world
set
, encrypt
, and decrypt
(#395)encrypt
, then decrypt
, then encrypt
on a json value (#377)Note: the underlying replace
engine to support these changes now wraps your values in single quotes. the prior replace
engine wrapped in double quotes.
So where your .env
used to look like this with double quotes:
HELLO="encrypted:1234"
API_KEY="encrypted:5678"
It will now begin looking like this with single quotes:
HELLO='encrypted:1234'
API_KEY='encrypted:5678'
It's an aesthetic side effect only. Your values will continue to be decrypted and encrypted correctly.