npm upgrade
Home@dotenvx/dotenvx 0 → 1
0.45.0 → 1.75.1. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@dotenvx/dotenvx 1.75.1 removes or renames exports your code may import.
- Removed
- 7
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 6
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @dotenvx/dotenvx@0.45.0..1.75.1
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- configDotenvobject
- convertobject
- decryptobject
- encryptobject
- settingsobject
- statusobject
- vaultEncryptobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 23, 2026. @dotenvx/dotenvx on lurq.