OpenTelemetry JavaScript SDK 2.0 — breaking‑change release that raises Node/TS baselines

Key update

OpenTelemetry has published JavaScript SDK 2.0 (the stable SDK packages and the 0.200.x unstable generation). The release raises the minimum supported Node.js to ^18.19.0 || >=20.6.0, requires TypeScript >=5.0.4, changes the public SDK interfaces (so SDK and some instrumentation packages are breaking), and moves the compiled target to ES2022 to improve tree‑shaking and bundle size. A migration guide and upgrade notes are provided by the maintainers. (opentelemetry.io)

Why it matters

Practically every Node/TypeScript service or library that relies on OpenTelemetry SDK packages (server tracing, metrics, auto‑instrumentation, exporters) faces a non‑trivial migration: you must ensure your runtime (Node) and toolchain (TypeScript/tsconfig) meet the new minimums, update vendor instrumentation (APM agents and community instrumentations may need upgrades), and run integration tests because public SDK APIs have changed. The payoff is smaller, more optimizable bundles, fewer runtime shims, and a simplified SDK surface that will accelerate future improvements — but the immediate impact is operational: staged upgrades, CI matrix changes, and possible temporary incompatibilities with older instrumentation. If you maintain libraries that depend on @opentelemetry/*, plan to update and publish compatible releases; if you run services, schedule a canary rollout after updating OTEL packages and Node versions and follow the official migration guide.

Source

• Source