Vigia

将 expo-calendar 从 57.x 升级到 58.x

根据 TypeScript 类型自动比较 expo-calendar 57.0.5 与 58.0.6 的公开 API。签名变化表示可能存在不兼容变更，并非确定结论。

概要

已删除的导入路径2
已删除的导出0
已修改的签名0
已删除的类或接口成员0
已修改的类或接口成员2
新增弃用0
要求变化（engines、peer 依赖）0
新增导出0

已删除的导入路径

已删除的导入路径
expo-calendar/next
expo-calendar/legacy

已删除的导出

未发现。

已修改的签名

未发现。

已删除的类或接口成员

未发现。

已修改的类或接口成员

member之前之后
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>

新增弃用

未发现。

要求变化（engines、peer 依赖）

未发现。

这些版本之间的 changelog

软件包作者发布的文本，按原样显示。

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))

把这些数据交给你的 AI 智能体

Vigia 是免费的 MCP 服务器：你的编程智能体在写代码之前就能检查版本、不兼容变更和安全漏洞。无需注册，无需 API 密钥。

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

添加到 Cursor添加到 VS Code★ 在 GitHub 上加星

任何其他 MCP 客户端
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

智能体技能（SKILL.md）：告诉智能体何时使用 Vigia · 用于拉取请求的 GitHub Action

常见问题

将 expo-calendar 从 57 升级到 58 有哪些不兼容变更？

在 expo-calendar 57.0.5 与 58.0.6 之间，Vigia 发现 0 个已删除的导出、0 个已修改的签名，以及 2 个已删除或修改的类或接口成员。

expo-calendar 58 中弃用了哪些内容？

expo-calendar 58.0.6 中有 0 个导出或成员新被标记为弃用。

供智能体使用

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