Upgrading @expo/steps from 25.x to 26.x
Comparison of the public API of @expo/steps 25.3.0 and 26.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 | 0 |
| Changed signatures | 0 |
| Removed class or interface members | 0 |
| Changed class or interface members | 1 |
| Newly deprecated | 0 |
| Requirement changes (engines, peer dependencies) | 0 |
| New exports | 0 |
Removed exports
None detected.
Changed signatures
None detected.
Removed class or interface members
None detected.
Changed class or interface members
| member | Before | After |
|---|---|---|
BuildStepGlobalContext.markAsCheckedOut | (logger: bunyan): void | (): void |
Newly deprecated
None detected.
Requirement changes (engines, peer dependencies)
None detected.
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 @expo/steps from 25 to 26?
Between @expo/steps 25.3.0 and 26.0.0, Vigia found 0 removed exports, 0 changed signatures and 1 removed or changed class or interface members.
What became deprecated in @expo/steps 26?
0 exports or members are newly marked as deprecated in @expo/steps 26.0.0.
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/@expo/steps/upgrade?from=25.3.0&to=26.0.0