Upgrading expo-linking from 57.x to 58.x

Comparison of the public API of expo-linking 57.0.13 and 58.0.13, 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	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	1

Removed exports

None detected.

Changed signatures

None detected.

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
`peerDependencies.expo`	`—`	`*`

New exports (1)

import	export	kind
`expo-linking`	`unwrapDevLaunchURL`	function

Changelog between these versions

Text published by the package authors, shown as-is.

58.0.13

### Patch Changes

- Updated dependencies.
  - expo-constants@58.0.12

58.0.12

### Patch Changes

- Updated dependencies.
  - expo-constants@58.0.11

58.0.11

### Patch Changes

- Updated dependencies.
  - expo-constants@58.0.10

58.0.10

### Patch Changes

- Bump precompiled artifacts due to ABI breakage in expo-modules-jsi@58.0.6. ([#50881](https://github.com/expo/expo/pull/50881) by [@kitten](https://github.com/kitten))

58.0.9

### Patch Changes

- Force-bump all packages, due to migration to changesets. ([#50762](https://github.com/expo/expo/pull/50762) by [@kitten](https://github.com/kitten))
- Stop decoding query parameter values twice in `parse()`. Values with percent-encoded `%`, `+` or `@` were altered, and malformed percent-encoding threw a `URIError`. ([#50289](https://github.com/expo/expo/pull/50289) by [@gabrieldonadel](https://github.com/gabrieldonadel))
- Add `unwrapDevLaunchURL()` to resolve the URL an app should route from an Expo Go or development build launch URL, dropping the reserved `__expo_*` params. ([#50289](https://github.com/expo/expo/pull/50289) by [@gabrieldonadel](https://github.com/gabrieldonadel))
- Updated dependencies. ([#50762](https://github.com/expo/expo/pull/50762), [#49511](https://github.com/expo/expo/pull/49511), [#50661](https://github.com/expo/expo/pull/50661))
  - expo-constants@58.0.9

58.0.8

_This version does not introduce any user-facing changes._

58.0.7

_This version does not introduce any user-facing changes._

58.0.6

_This version does not introduce any user-facing changes._

58.0.5

_This version does not introduce any user-facing changes._

58.0.4

### 🎉 New features

- [iOS] Ignore the fingerprint-check trigger URL, so it never becomes the initial URL `getLinkingURL()` returns. ([#49494](https://github.com/expo/expo/pull/49494) by [@vonovak](https://github.com/vonovak))

58.0.3

_This version does not introduce any user-facing changes._

58.0.2

_This version does not introduce any user-facing changes._

58.0.1

_This version does not introduce any user-facing changes._

58.0.0

### 🐛 Bug fixes

- Create development deep links from the bundle URL's authority instead of the manifest's `hostUri` ([#48275](https://github.com/expo/expo/pull/48275) by [@kitten](https://github.com/kitten))

### 💡 Others

- [Internal] Read the development server URL from `expo/internal/bundle-origin` instead of duplicating its accessor ([#48278](https://github.com/expo/expo/pull/48278) by [@kitten](https://github.com/kitten))

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 Cursor Add 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-linking from 57 to 58?

Between expo-linking 57.0.13 and 58.0.13, Vigia found 0 removed exports, 0 changed signatures and 0 removed or changed class or interface members.

What became deprecated in expo-linking 58?

0 exports or members are newly marked as deprecated in expo-linking 58.0.13.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/expo-linking/upgrade?from=57.0.13&to=58.0.13