@dotenvx/dotenvx - npm Package Versions

1.20.0

Changed

• respect process.env.DOTENV_PRIVATE_KEY and/or process.env.DOTENV_PUBLIC_KEY on set (#401)
• respect process.env.DOTENV_PRIVATE_KEY and/or process.env.DOTENV_PUBLIC_KEY on encrypt (#411)
• respect process.env.DOTENV_PRIVATE_KEY on decrypt (#412)
• change logger.help to use brighter blue (#414)

Removed

• remove main.decrypt,encrypt,set (#410)

1.19.3

Changed

• 🐞 fix decrypt re-encrypt of values containing backslashes (#406)

1.19.2

Changed

• forward additional signals like SIGUSR2 (#403)

1.19.1

Changed

• if SIGTERM or SIGINT sent, don't bubble wrapped process error (#402)

1.19.0

Added

• support key glob filtering for encrypt and decrypt. example: dotenvx encrypt -ek "NEXT_PUBLIC_*" (#397)

1.18.1

Added

• escape user inputted regex groupings like $1 or $2. (#396)

1.18.0

Added

• set and encrypt preserve leading spaces (#395)

     HELLO=world

Changed

• improve escape and quote handling for set, encrypt, and decrypt (#395)
• 🐞 fix 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.

1.17.0

Added

• add --format=eval option for get (#393)

1.16.1

Changed

• suppress stderr using options.stdio (#391)

1.16.0

Changed

• for dotenvx keypair call out to dotenvx pro keypair if pro installed (#390)