@opentelemetry/resources breaking changes
Every breaking API change we have recorded in @opentelemetry/resources on npm: 10 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.
Newest change October 20, 2026
On this page
3.0.0
- Removed
The minimum supported Node.js is now 22.15.0, so code running on Node.js 18 or 20 must upgrade. github.com - Removed
The minimum supported Node.js version is raised to 22.15.0. Upgrade Node.js before using this release. github.com - Removed
Imports such as @opentelemetry/core/build/... now fail; use the documented exports instead. github.com - Removed
Packages now define entry points via the exports field in package.json. Deep imports into internal paths break, and <package>/package.json is no longer importable; use SDK_INFO from @opentelemetry/core for the SDK version. github.com - Removed
detectors.platform
Import platform detectors from the package root instead of the removed subpath. github.com - Removed
detectors.platform.browser
Import browser platform detectors from the package root instead of the removed subpath. github.com - Behavior changed
Resources now accept only simple attribute values. Complex values such as objects or arrays of mixed types are dropped with a warning, so convert them to simple values. github.com - Configuration changed
Bundlers without imports support fail to resolve the package; check the migration guide. github.com - Configuration changed
The package no longer ships a top-level browser field and selects Node.js or browser code through exports and imports conditions. Bundlers must support the imports and exports fields, with minimum versions listed in the guide. github.com - Signature changed
RawResourceAttribute
Was type RawResourceAttribute = [string, MaybePromise<AttributeValue | undefined>]; now type RawResourceAttribute = [string, MaybePromise<AnyValue | undefined>]. npmjs.com
Check your code
These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.
Put your code on continuous management.
Scan a public repository now, or give your agent one line.
See how out of date your code is.
Tell your agent what changed since it was trained.
claude mcp add --transport http since https://api.since.dev/mcp