Skip to content

Deno's export surface is narrower than Cloudflare's #23896

Description

@isaacs

Cloudflare runs on workerd with no Node APIs, and still exports more than Deno. Missing from packages/deno/src/index.ts but present in packages/cloudflare/src/index.ts:

Missing from Deno Comes from
instrumentOpenAiClient, instrumentAnthropicAiClient, instrumentGoogleGenAIClient, instrumentLangChainEmbeddings, instrumentStateGraph, createLangChainCallbackHandler, instrumentCreateReactAgent @sentry/server-utils (already a dependency)
prismaIntegration @sentry/server-utils
trpcMiddleware, addIntegration, withActiveSpan, getSpanDescendants, setConversationId, parameterize, consoleIntegration, createConsolaReporter, growthbookIntegration, updateSpanName @sentry/core
spotlightIntegration, httpServerIntegration needs a decision, may not apply
initWithoutDefaultIntegrations, getDefaultIntegrationsWithoutPerformance Node and Bun both have these

The manual AI-client helpers matter most. They are the documented fallback for when channel injection is unavailable, which per D2 is Deno's default state.

Work item. Add the @sentry/core and @sentry/server-utils re-exports. They are pure re-exports with no new code. Add initWithoutDefaultIntegrations to deno/src/sdk.ts.

**Prior art **(related history only). No issue. Related history: #22306 (closed) covered pulling the integrations themselves into Deno, and the feat(deno): add * integration series (#22448 through #22472, all merged) added them one by one. The manual instrument*Client helpers were never part of that sweep.

Metadata

Metadata

Assignees

No one assigned

    Labels

    DenojavascriptPull requests that update javascript code

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions