Upgrading expo-image-manipulator from 57.x to 58.x

Comparison of the public API of expo-image-manipulator 57.0.21 and 58.0.14, 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	1
Removed class or interface members	0
Changed class or interface members	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	2
New exports	1

Removed exports

None detected.

Changed signatures

export	Before	After
`expo-image-manipulator · useImageManipulator`	`(source: any): ImageManipulatorContext`	`(source: any, options?: ImageLoadOptions \| undefined): ImageManipulatorContext`

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

New exports (1)

import	export	kind
`expo-image-manipulator`	`ImageLoadOptions`	type

Changelog between these versions

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

58.0.14

### Patch Changes

- [Internal] Bump precompiled artifacts due to ABI breakage in expo-modules-jsi, which makes `JavaScriptValue` a non-copyable struct. ([#51368](https://github.com/expo/expo/pull/51368) by [@tsapeta](https://github.com/tsapeta))
- [Android] Fix `renderAsync()` rejecting with `JobCancellationException` when the context is released while the render is still pending, for example when a component using `useImageManipulator` unmounts mid-render. ([#50218](https://github.com/expo/expo/pull/50218) by [@dev-eyoungmin](https://github.com/dev-eyoungmin))

58.0.13

### Patch Changes

- Bump precompiled artifacts due to ABI breakage in expo-modules-core@58.0.13. ([#51138](https://github.com/expo/expo/pull/51138) by [@alanjhughes](https://github.com/alanjhughes))

58.0.12

### Patch Changes

- [iOS] Added missing `import UIKit` statements so the module builds from source with Swift Package Manager. ([#50961](https://github.com/expo/expo/pull/50961) by [@chrfalch](https://github.com/chrfalch))

58.0.11

### 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))
- Updated dependencies. ([#50881](https://github.com/expo/expo/pull/50881))
  - expo-image-loader@58.0.3

58.0.10

### 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))
- Updated dependencies. ([#50762](https://github.com/expo/expo/pull/50762))
  - expo-image-loader@58.0.2

58.0.9

### 🐛 Bug fixes

- [iOS] Fixed `renderAsync` failing with `ERR_IMAGE_CONTEXT_LOST` for 10-bit HDR images, such as HEIC screenshots. ([#50011](https://github.com/expo/expo/pull/50011) by [@expo-bot](https://github.com/expo-bot))
- [iOS] Keep the full pixel resolution of images loaded with a scale factor greater than 1 instead of downscaling them to their point size. ([#50011](https://github.com/expo/expo/pull/50011) by [@vonovak](https://github.com/vonovak))

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

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

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

### 🎉 New features

- Added `maxWidth`/`maxHeight` options to `ImageManipulator.manipulate` and `useImageManipulator` that downsample large images while decoding, significantly reducing the peak memory usage and avoiding out-of-memory crashes. ([#47877](https://github.com/expo/expo/pull/47877) by [@jiunshinn](https://github.com/jiunshinn))

### 🐛 Bug fixes

- [Web] Fixed `release()` not releasing image manipulation resources. ([#49831](https://github.com/expo/expo/pull/49831) by [@mozzius](https://github.com/mozzius))
- Fixed `ImageManipulator.Image` being typed as an `ImageRef` instance rather than the class it holds at runtime, which rejected `instanceof` checks and made instance members appear to exist on it. ([#48613](https://github.com/expo/expo/pull/48613) by [@vonovak](https://github.com/vonovak))

### 💡 Others

- Add missing `react` and `react-native` peer dependencies ([#49744](https://github.com/expo/expo/pull/49744) by [@kitten](https://github.com/kitten))

### 📚 3rd party library updates

- Bump `SDWebImage` to 5.21.6 and `SDWebImageWebPCoder` to 0.15.0 to align with `expo-image` ([#49744](https://github.com/expo/expo/pull/49744) 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-image-manipulator from 57 to 58?

Between expo-image-manipulator 57.0.21 and 58.0.14, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in expo-image-manipulator 58?

0 exports or members are newly marked as deprecated in expo-image-manipulator 58.0.14.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/expo-image-manipulator/upgrade?from=57.0.21&to=58.0.14