Upgrading envalid from 8.x to 9.x
Comparison of the public API of envalid 8.2.0 and 9.0.0, 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 | 1 |
| Removed class or interface members | 0 |
| Changed class or interface members | 0 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 1 |
| New exports | 0 |
Removed exports
| import | export | kind | Before |
|---|---|---|---|
envalid | testOnly | variable | <T>(defaultValueForTests: T): T |
Changed signatures
| export | Before | After |
|---|---|---|
envalid · RequiredValidatorSpec | RequiredSpec<T> & WithParser<T> | Spec<T> & RequiredAttrs<T> & WithParser<T> |
Removed class or interface members
None detected.
Changed class or interface members
None detected.
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
| Before | After | |
|---|---|---|
engines.node | >=18 | >=22 |
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What are the breaking changes when upgrading envalid from 8 to 9?
Between envalid 8.2.0 and 9.0.0, Vigia found 1 removed exports, 1 changed signatures and 0 removed or changed class or interface members.
What became deprecated in envalid 9?
0 exports or members are newly marked as deprecated in envalid 9.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/envalid/upgrade?from=8.2.0&to=9.0.0