Vigia

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

Comparison of the public API of expo-calendar 57.0.5 and 58.0.6, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths2
Removed exports0
Changed signatures0
Removed class or interface members0
Changed class or interface members2
Newly deprecated0
Requirement changes (engines, peer dependencies)0
New exports0

Removed import paths

Removed import paths
expo-calendar/next
expo-calendar/legacy

Removed exports

None detected.

Changed signatures

None detected.

Removed class or interface members

None detected.

Changed class or interface members

memberBeforeAfter
ExpoCalendarEvent.editInCalendar(params?: CalendarDialogParamsNext | null | undefined): Promise<DialogEventResult>(params?: CalendarDialogParamsNext | undefined): Promise<DialogEventResult>
ExpoCalendarEvent.openInCalendar(params?: CalendarDialogOpenParamsNext | null | undefined): Promise<OpenEventDialogResult>(params?: CalendarDialogOpenParamsNext | undefined): Promise<OpenEventDialogResult>

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

None detected.

Changelog between these versions

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

58.0.6
### 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.5
### 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))
58.0.4
_This version does not introduce any user-facing changes._
58.0.3
### 🐛 Bug fixes

- [Android] Fix the sign of alarm `relativeOffset` in the `next` API so that negative values fire before the event start, matching iOS and the legacy API.
58.0.2
### 🐛 Bug fixes

- [iOS] Allow `getDefaultCalendarSync`, `getCalendars` and `ExpoCalendar.get` to work with write-only calendar access. ([#48186](https://github.com/expo/expo/pull/48186) by [@Wenszel](https://github.com/Wenszel))
58.0.1
### 🛠 Breaking changes

- The `params` argument of `openInCalendar()` and `editInCalendar()` no longer accepts `null`. Call the methods with no arguments instead. ([#50158](https://github.com/expo/expo/pull/50158) by [@Wenszel](https://github.com/Wenszel))
58.0.0
### 🐛 Bug fixes

- [android] Fix `createEventAsync` and `updateEventAsync` failing with "Event could not be saved" in minified release builds. `EventInputBase` now implements `Record`, so the `expo-modules-core` ProGuard rule keeps its `@Field` property names and `startDate`/`endDate` reach the calendar provider. ([#49837](https://github.com/expo/expo/pull/49837) by [@expo-bot](https://github.com/expo-bot))
- [android] Fix `openInCalendar()` throwing when called without params, which the type declares as optional. ([#50146](https://github.com/expo/expo/pull/50146) by [@hknakn](https://github.com/hknakn))
- [ios] Fix a crash when reading `calendarId` on an event or reminder whose `EKCalendarItem.calendar` is nil. The property is `null_unspecified` in the EventKit headers, so the bare access was an implicit force-unwrap that trapped the JS thread. ([#48445](https://github.com/expo/expo/pull/48445) by [@cvburgess](https://github.com/cvburgess))
- [ios] Fix typo in the internal permissions exception name (`MissionPermissionsException` -> `MissingPermissionsException`), which corrects the error code surfaced to JS from `ERR_MISSION_PERMISSIONS` to `ERR_MISSING_PERMISSIONS`. ([#47804](https://github.com/expo/expo/pull/47804) by [@conanm](https://github.com/conanm))

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-calendar from 57 to 58?

Between expo-calendar 57.0.5 and 58.0.6, Vigia found 0 removed exports, 0 changed signatures and 2 removed or changed class or interface members.

What became deprecated in expo-calendar 58?

0 exports or members are newly marked as deprecated in expo-calendar 58.0.6.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/expo-calendar/upgrade?from=57.0.5&to=58.0.6