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

Abierto
  • ¿Algo no está bien?
#10,328 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@effect-bot ya está trabajando en esto.

Desde el 3/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
16.7k
Forks
808
Merge medio
11 h 3 min
PR fusionados (30 d)
839

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Effect-TS/effect

Todos los issues de Effect-TS/effect

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.