npm · npm:expo-updates
expo-updates active
Fetches and manages remotely-hosted assets and updates to your app's JS bundle.
The latest stable version of expo-updates is 58.0.22, published on 2026-11-11. Verified by Vigia on 2026-11-12.
| Latest stable version | 58.0.22 |
|---|---|
| Published | 2026-11-11 14:18:08 UTC |
| Install | npm install expo-updates@latest |
| Requires (engines) | none declared |
| Peer dependencies | expo * react * react-native * expo-dev-client * |
| Dist-tags | next: 58.0.17 canary: 58.0.0-canary-20260909-ea7a89a latest: 58.0.22 sdk-50: 0.24.11 sdk-52: 0.27.5 sdk-53: 0.28.18 sdk-54: 29.0.20 sdk-55: 55.0.33 sdk-56: 56.0.28 sdk-57: 57.0.28 canary-sdk-55: 55.0.12-canary-20260429-a5e59cf canary-sdk-56: 56.0.18-canary-20260701-9100865 |
| License | MIT |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 18:24:19 UTC |
| Sources | api.deps.dev, registry.npmjs.org, registry.npmjs.org |
Ask your AI assistant to check this
AI models are trained up to a date, so they can be wrong about versions, deprecations and vulnerabilities. Paste this into Claude, ChatGPT, Perplexity or Cursor and it will answer with the verified data on this page:
Before answering about the npm package "expo-updates", check Vigia (verified, dated facts): https://vigia.coredls.cloud/v1/packages/npm/expo-updates . For my whole project use https://vigia.coredls.cloud/context
Using an AI coding agent every day? Connect Vigia once and it checks this by itself.
Maintenance
| Activity | active |
|---|---|
| Last stable release | 2026-11-05 09:32:56 UTC · 7 days ago |
| Stable releases in the last 12 months | 123 |
| Published versions | 521 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
57.0.27 | 2026-11-05 09:32:56 UTC |
58.0.21 | 2026-11-03 16:35:04 UTC |
58.0.20 | 2026-10-31 10:19:45 UTC |
58.0.19 | 2026-10-28 15:33:03 UTC |
58.0.18 | 2026-10-21 18:16:46 UTC |
58.0.17 | 2026-10-15 19:40:36 UTC |
58.0.16 | 2026-10-13 09:09:04 UTC |
57.0.26 | 2026-10-12 14:28:23 UTC |
57.0.25 | 2026-10-06 12:07:16 UTC |
58.0.15 | 2026-10-05 22:22:40 UTC |
58.0.14 | 2026-10-03 13:02:59 UTC |
58.0.13 | 2026-10-01 19:30:12 UTC |
58.0.12 | 2026-10-01 09:25:12 UTC |
58.0.11 | 2026-09-29 15:18:26 UTC |
55.0.33 | 2026-09-29 11:30:22 UTC |
56.0.28 | 2026-09-29 11:22:27 UTC |
57.0.24 | 2026-09-29 10:56:36 UTC |
55.0.32 | 2026-09-28 16:11:32 UTC |
58.0.10 | 2026-09-28 12:29:18 UTC |
58.0.9 | 2026-09-25 08:22:51 UTC |
Showing the 20 most recent of 350 versions. JSON
Upgrade guides for this package
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 is the latest version of expo-updates?
The latest stable version of expo-updates is 58.0.22, published on 2026-11-11. Verified by Vigia on 2026-11-12.
How do I install the latest version of expo-updates?
Run npm install expo-updates@latest. The latest stable version is 58.0.22 (verified 2026-11-12).
Is expo-updates deprecated?
No. expo-updates is not marked as deprecated in the registry.
Which Node.js version does expo-updates require?
expo-updates 58.0.22 does not declare a Node.js version requirement.
Does expo-updates 58.0.22 have known vulnerabilities?
No known advisories affect expo-updates 58.0.22 according to the data Vigia checks.
Is expo-updates still maintained?
expo-updates published 123 stable releases in the last 12 months; the most recent was 7 days ago. Activity: active.
Observed changes
- Wed Nov 11 2026 18:24:00 GM +0000 (Coordinated Universal Time) — released 58.0.22 → 58.0.22
- Wed Nov 11 2026 14:23:56 GM +0000 (Coordinated Universal Time) — released 58.0.21 → 58.0.22
- ue Nov 03 2026 18:20:43 GMT+0000 (Coordinated Universal Time) — released 58.0.20 → 58.0.21
- Sat Oct 31 2026 12:19:39 GM +0000 (Coordinated Universal Time) — released 58.0.19 → 58.0.20
- Wed Oct 28 2026 16:18:36 GM +0000 (Coordinated Universal Time) — released 58.0.18 → 58.0.19
- Wed Oct 21 2026 19:56:46 GM +0000 (Coordinated Universal Time) — released 58.0.17 → 58.0.18
- hu Oct 15 2026 21:51:12 GMT+0000 (Coordinated Universal Time) — released 57.0.26 → 58.0.17
- Mon Oct 12 2026 15:47:50 GM +0000 (Coordinated Universal Time) — released 57.0.25 → 57.0.26
Related packages
- expo
- expo-dev-client
- react
- react-native
- @ethersproject/sha2
- @aws-sdk/client-ec2
- @storybook/cli
- cross-dirname
- eslint-plugin-react-compiler
- postcss-html
- @vercel/stega
- jayson
- set-immediate-shim
- shallow-copy
- @valibot/to-json-schema
- stream-parser
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/expo-updates) [](https://vigia.coredls.cloud/npm/expo-updates) [](https://vigia.coredls.cloud/npm/expo-updates)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/expo-updates
GET https://vigia.coredls.cloud/v1/packages/npm/expo-updates/versions/{version}