@apicurio/apicurio-registry-sdk

中文文档
3.3.4发布于 2026/11/04TypeScriptES Module零依赖构建来源已验证近 30 天下载 5061

This library provides an SDK for Apicurio Registry for use in Node.js and front-end (UI) applications. It is written in Typescript using Kiota to generate the REST client.

原始使用文档
文档目录3 节
  1. Building
  2. Release Notes
  3. Behavioral Change: Requests Are Now Compressed By Default

Apicurio Registry Typescript SDK

This library provides an SDK for Apicurio Registry for use in Node.js and front-end (UI) applications. It is written in Typescript using Kiota to generate the REST client.

Building

Use standard Node/NPM tooling to build the code in this library.

npm install
npm run generate-sources
npm run lint
npm run build

Release Notes

Behavioral Change: Requests Are Now Compressed By Default

RegistryClientFactory.createRegistryClient() now builds its default middleware chain from Kiota's MiddlewareFactory.getPerformanceMiddlewares(), which adds a CompressionHandler on top of the previous default chain (retry, redirect, parameter decoding, user agent, headers inspection). As a result, outgoing request bodies are now gzip-compressed (Content-Encoding: gzip) by default, matching the server's enable-decompression support.

This is a behavioral change for existing callers of createRegistryClient(): any custom middlewares you pass are still appended after the defaults (this was already true before this change — passing middlewares never replaced the defaults), but the defaults themselves now compress request bodies where they previously did not.

If you need to opt out (e.g. to fully control the middleware chain yourself, or to talk to a server that doesn't support decompression), pass useDefaultMiddlewares = false as the fourth argument:

RegistryClientFactory.createRegistryClient(baseUrl, authProvider, customMiddlewares, false);

With useDefaultMiddlewares = false, customMiddlewares is used as-is with no defaults added.

版本与发布记录

@apicurio/apicurio-registry-sdk 共发布 35 个版本,首次发布于 2024/09/19;过去 12 个月发布了 14 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
3.3.4latest2026/11/044 天前
3.3.32026/09/091 个月前
3.3.22026/08/282 个月前
3.3.12026/07/283 个月前
3.3.02026/06/094 个月前
3.2.52026/06/045 个月前

关于 @apicurio/apicurio-registry-sdk 的常见问题

@apicurio/apicurio-registry-sdk 是什么?

This library provides an SDK for Apicurio Registry for use in Node.js and front-end (UI) applications. It is written in Typescript using Kiota to generate the REST client.

如何安装 @apicurio/apicurio-registry-sdk?

在项目目录运行 npm install @apicurio/apicurio-registry-sdk,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:@microsoft/kiota-abstractions(1.0.0-preview.112)、@microsoft/kiota-http-fetchlibrary(1.0.0-preview.112)、@microsoft/kiota-serialization-form(1.0.0-preview.112)、@microsoft/kiota-serialization-json(1.0.0-preview.112)、@microsoft/kiota-serialization-text(1.0.0-preview.112)、@microsoft/kiota-serialization-multipart(1.0.0-preview.112)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@apicurio/apicurio-registry-sdk 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@apicurio/apicurio-registry-sdk 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@apicurio/apicurio-registry-sdk 可以商用吗?

@apicurio/apicurio-registry-sdk 使用 未声明 许可。package.json 没有声明许可证。没有许可证的代码默认保留全部权利,商用前请联系作者或查看仓库中的 LICENSE 文件。以上为概括,不构成法律意见,请以许可原文为准。

@apicurio/apicurio-registry-sdk 的下载量有多少?

根据 npm 官方下载统计,@apicurio/apicurio-registry-sdk 在 2026/10/06 – 2026/11/04 这 30 天内被下载 5,061 次,日均约 169 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@apicurio/apicurio-registry-sdk 还在维护吗?

最新版本 3.3.4 发布于 2026/11/04(4 天前);至今共发布 35 个版本,其中过去 12 个月发布了 14 个;首次发布于 2024/09/19。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。