@dotenvx/primitives
4.4.0 · 6 Nov 2026BSD-3-Clause18.4M / weekRepositorynpmAtom feed
Upgrading @dotenvx/primitives From 1.4.0 to 1.10.0
11 releases in betweennotes for 7
Reading releases, release notes and advisories…
- 8+
- changes to make
- 0
- advisories fixed
- 9+
- new
- ?
- fixes
Counted from 7 of 11 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Breaking1.10.0
- Breaking1.9.0
- Breaking1.8.0
- Breaking1.8.0
- Breaking1.7.0
- Breaking1.6.0
- Breaking1.6.0
- Breaking1.5.0
Release by release
- Breaking
Remove
dotenvx ext vault, replace with dotenvx-ext-vault (install there to continue usingext vault)
- Breaking
- Breaking
Removed
winston- logger simplified to useconsole.loggoing forward - New
Add
--exclude-key(-ek) option todotenvx encryptanddotenvx decrypt
- Breaking
1.8.1no release note
1.7.1 – 1.7.22 releases, no release note
- New
Add support for
.env1(.env*) file format. (private key expands toDOTENV_PRIVATE_KEY_DEVELOPMENT1)
- New
- Breaking
Remove
dotenvx convert- still atdotenvx encrypt - Breaking
Remove
dotenvx vault- still atdotenvx ext vault - New
Add
dotenvx decryptcommand. works inversely todotenvx encrypt. same flags. - New
Add
--stdoutoption todotenvx decrypt. example:dotenvx decrypt -f .env.production --stdout > somefile.txt - New
Add
--stdoutoption todotenvx encrypt. example:dotenvx encrypt -f .env.production --stdout > somefile.txt
- Breaking
6 other lines we could not sort, mostly version bumps
- 1.9.0
Preserve comments and spacing on first-time generation of .env.example file
- 1.8.0
Use
ansicolors overrgb- for wider terminal coverage - 1.8.0
Replace
chalkwithpicocolorsandcolor-name- cutting down on 5 dependencies - 1.8.0
Replace
execawithtinyexec- cutting down on 15 dependencies - 1.6.0
Smarter private key finder. if you rename your file to
secrets.txtit can still decrypt fromDOTENV_PRIVATE_KEYby seeking out the invert of theDOTENV_PUBLIC_KEYinsidesecrets.txt - 1.5.0
Replace
@inquirer/confirmandora
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.