Support OpenTelemetry JS SDK v3 and replace deprecated tracing peers in Effect v4

Aperta
  • Qualcosa non va?
#10,328 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@effect-bot ci sta già lavorando.

Dal 3/11/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

What is the problem this feature would solve?

@effect/[email protected] still targets OpenTelemetry JS SDK 2.x, while upstream released SDK 3.0.0 on October 20, 2026. The same restrictions are present on Effect's current main.

The package manifest declares:

  • @opentelemetry/resources and @opentelemetry/sdk-metrics: >=2.0.0 <3.0.0, excluding the current 3.0.0 releases.
  • @opentelemetry/sdk-logs: >=0.203.0 <0.300.0, excluding its newly stable 3.0.0 release.
  • @opentelemetry/sdk-trace-base, @opentelemetry/sdk-trace-node, and @opentelemetry/sdk-trace-web: >=2.0.0 <3.0.0. All three packages are now deprecated on npm, with a notice directing users to @opentelemetry/sdk-trace. Their latest versions remain 2.12.0; the replacement package is 3.0.0.
  • @opentelemetry/api-logs: still a peer, although upstream removed the standalone package in SDK 3.x and moved its APIs into @opentelemetry/[email protected]. Its latest npm version is not marked deprecated, so this is distinct from the three tracing packages above.

This prevents applications from upgrading to the current SDK within Effect's declared peer ranges and keeps the integration tied to retired tracing packages.

References:

What is the feature you are proposing to solve the problem?

Add OpenTelemetry JS SDK 3.x support to the Effect v4 integration:

  • Migrate tracing imports, providers, and peer dependencies to @opentelemetry/sdk-trace.
  • Migrate logs API imports to @opentelemetry/api and support stable @opentelemetry/sdk-logs@3.
  • Update the remaining SDK peer ranges and development dependencies after checking upstream breaking changes.
  • Update examples and verify Node/browser tracing, metrics, and logging against the supported SDK versions.

This report is based on repository and published npm metadata inspection, not a runtime reproduction.

What alternatives have you considered?

Keep a consistent OpenTelemetry 2.x dependency set for now. Overriding peer ranges alone does not address removed packages or API changes.

Lingua principale
TypeScript
Stelle
16.7k
Fork
808
Merge medio
11h 3m
PR unite (30g)
839

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Effect-TS/effect

Tutte le issue di Effect-TS/effect

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.