Vigia

将 react-native-keychain 从 10.x 升级到 11.x

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

概要

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

已删除的导出

未发现。

已修改的签名

export之前之后
react-native-keychain · Result{ service: string; storage: STORAGE_TYPE; }{ service: string; storage: STORAGE_TYPE | "keychain"; }
react-native-keychain · default{ SECURITY_LEVEL: typeof SECURITY_LEVEL; ACCESSIBLE: typeof ACCESSIBLE; ACCESS_CONTROL: typeof ACCESS_CONTROL; AUTHENTICATION_TYPE: typeof AUTHENTICATION_TYPE; BIOMETRY_TYPE: typeof BIOMETRY_TYPE; STORAGE_TYPE: typeof STORAGE_TYPE; getSecurityLevel: (options?: AccessControlOption | undefined) => Promise<SECURITY_LEVEL | null>; canImplyAuthentication: (options?: AuthenticationTypeOption | undefined) => Promise<boolean>; getSupportedBiometryType: () => Promise<BIOMETRY_TYPE | null>; setInternetCredentials: (server: string, username: string, password: string, options?: SetOptions | undefined) => …{ SECURITY_LEVEL: typeof SECURITY_LEVEL; ACCESSIBLE: typeof ACCESSIBLE; ACCESS_CONTROL: typeof ACCESS_CONTROL; AUTHENTICATION_TYPE: typeof AUTHENTICATION_TYPE; BIOMETRY_TYPE: typeof BIOMETRY_TYPE; STORAGE_TYPE: typeof STORAGE_TYPE; ERROR_CODE: typeof ERROR_CODE; getSecurityLevel: (options?: AccessControlOption | undefined) => Promise<SECURITY_LEVEL | null>; canImplyAuthentication: (options?: AuthenticationTypeOption | undefined) => Promise<boolean>; getSupportedBiometryType: () => Promise<BIOMETRY_TYPE | null>; setInternetCredentials: (server: string, username: string, password: string, option…
react-native-keychain · SharedWebCredentials{ server: string; } & { username: string; password: string; } & Result{ server: string; } & Omit<UserCredentials, "service">
react-native-keychain · getInternetCredentials(server: string, options?: GetOptions | undefined): Promise<false | UserCredentials>(server: string, options?: GetOptions | undefined): Promise<false | InternetCredentials>
react-native-keychain · hasInternetCredentials(options: string | BaseOptions): Promise<boolean>(options: BaseOptions): Promise<boolean>
react-native-keychain · setSharedWebCredentials(server: string, username: string, password?: string | undefined): Promise<void>(server: string, username: string, password?: string | undefined): Promise<boolean>
react-native-keychain · resetInternetCredentials(options: BaseOptions): Promise<void>(options: BaseOptions): Promise<boolean>

已删除的类或接口成员

未发现。

已修改的类或接口成员

未发现。

新增弃用

未发现。

要求变化（engines、peer 依赖）

之前之后
engines.node>=16>=20.19.4
peerDependencies.react—>=19.1.1
peerDependencies.react-native—>=0.82.0
新增导出 (4)
importexportkind
react-native-keychainERROR_CODEenum
react-native-keychainInternetCredentialstype
react-native-keychaingetAllInternetCredentialServersfunction
react-native-keychainGetAllInternetCredentialServersOptionstype

把这些数据交给你的 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

常见问题

将 react-native-keychain 从 10 升级到 11 有哪些不兼容变更？

在 react-native-keychain 10.0.0 与 11.0.0 之间，Vigia 发现 0 个已删除的导出、7 个已修改的签名，以及 0 个已删除或修改的类或接口成员。

react-native-keychain 11 中弃用了哪些内容？

react-native-keychain 11.0.0 中有 0 个导出或成员新被标记为弃用。

供智能体使用

GET https://vigia.coredls.cloud/v1/packages/npm/react-native-keychain/upgrade?from=10.0.0&to=11.0.0