Upgrading dotenv from 17.x to 18.x
Comparison of the public API of dotenv 17.4.2 and 18.0.5, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.
Summary
| Removed import paths | 0 |
|---|---|
| Removed exports | 1 |
| Changed signatures | 2 |
| Removed class or interface members | 1 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 1 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
dotenv | decrypt | function | (encrypted: string, keyStr: string): string |
Changed signatures
| export | Before | After |
|---|---|---|
dotenv · parse | <T extends DotenvParseOutput = DotenvParseOutput>(src: any): T | <T extends DotenvParseOutput = DotenvParseOutput>(src: any, options?: DotenvParseOptions | undefined): T |
dotenv · DotenvError | Error & { code: "MISSING_DATA" | "INVALID_DOTENV_KEY" | "NOT_FOUND_DOTENV_ENVIRONMENT" | "DECRYPTION_FAILED" | "OBJECT_REQUIRED"; } | Error & { code: "OBJECT_REQUIRED" | (string & {}); } |
Removed class or interface members
| member | import | Before |
|---|---|---|
DotenvConfigOptions.DOTENV_KEY | dotenv | string | undefined |
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
New exports (1)
| import | export | kind |
|---|---|---|
dotenv | DotenvParseOptions | interface |
Frequently asked questions
What are the breaking changes when upgrading dotenv from 17 to 18?
Between dotenv 17.4.2 and 18.0.5, Vigia found 1 removed exports, 2 changed signatures and 1 removed or changed class or interface members.
What became deprecated in dotenv 18?
0 exports or members are newly marked as deprecated in dotenv 18.0.5.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/dotenv/upgrade?from=17.4.2&to=18.0.5