dotenv-expand
1000.0.0 · 29 Jul 2026BSD-3-Clause62.5M / weekRepositoryHomepagenpmAtom feed
Upgrading dotenv-expand From 9.0.0 to 1000.0.0
15 releases in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 10
- new
- 3
- fixes
Before you upgrade
Tick each one off as you go- Breaking1000.0.0
- Breaking12.0.0
- Breaking11.0.0
Release by release
- Breaking
Require Node.js 16 or later.
- New
NEW 🎉: Command substitution and encryption are now supported automatically during expansion.
- Fixed
FIXED: Correct empty-variable expansion to distinguish between variables that are unset (
-and+) and variables that are empty (:-and:+).
- Breaking
13.0.0nothing new or fixed in the note
12.0.1nothing new or fixed in the note
11.0.7nothing new or fixed in the note
- Fixed
Fix
.nyc_outputin.npmignore
- Fixed
10 other lines we could not sort, mostly version bumps
- 1000.0.0
License updated from BSD-2-Clause to BSD-3-Clause.
- 12.0.1
Break logic on runningParsed (#ad887)
- 12.0.0
🎉 Expansion logic rewritten to match dotenvx
- 11.0.7
🐞 fix self-expanding undefined variable with default value
- 11.0.5
🐞 fix recursive expansion when expansion key is sourced from
process.env - 11.0.4
🐞 fix recursive expansion when expansion keys in reverse order
- 11.0.3
🐞 bug fix when
processEnvset to process.env rather than empty object (also test fixes which hid the bug) - 11.0.2
Changed funding link in package.json to
dotenvx.com - 11.0.0
- 11.0.0
🐞 fix fatal recursive error when variable defines value with same variable
VAR=$VAR#98
1 internal line (docs, tests, tooling) left out.
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.