Move the shared API client into @sentry/api #1875

Part of #1357. Plan: unify-sentry-api-layer task 8.5 (tasks, proposal PR #1669).

Why

The shared client (errors, apiPath, response validation, pagination, cache policy, retry policy, transport, request core) lives in packages/toolkit-core/src/api-client/. @sentry/api (getsentry/sentry-api-schema) already has hand-written client code of its own in lib/ (browser-client.ts, sentry-errors.ts, sentry-pagination.ts). Two copies of the same layer is the thing this workstream exists to remove, and every later step (CLI wrappers, sentry schema on the operation catalog, the hosted SDK) builds on one client in @sentry/api.

Scope

The work lands in getsentry/sentry-api-schema.

• Move toolkit-core/src/api-client/ into the package's lib/.
• Reconcile it with what is already there, so the package ends with one error type, one pagination helper, and one transport.
• Keep the injected interfaces (credentials, CacheStore, fresh-read scope, logger, span hook) and the portability rules from ref(toolkit-core): Start the shared API client with errors and response reading #1732: no node:* imports or Node globals in the shared modules. Host storage, such as the node:zlib cache codec, stays in toolkit.
• Publish a new @sentry/api version.

Done when

• The package's tests pass.
• Its browser entry builds and makes a request against a mocked fetch.
• A new @sentry/api version is on npm.

Next: switching toolkit to it and deleting the toolkit-core copy is a separate issue.

via @BYK.

--

View Session in Sentry