# What changed in @opentelemetry/api-logs

> 4 changes in @opentelemetry/api-logs 3 from its official release notes, upgrade guides and advisories: 3 breaking. Each one cited. Sources checked 2026-10-27. HTML: https://unstale.sh/npm/@opentelemetry/api-logs/

To see which of these apply to a repository, run `npx @unstale/cli init` in it.

## @opentelemetry/api-logs 3

### Breaking changes

- Package builds now declare an exports map. Deep imports into build output and imports of a package's package.json no longer resolve; use listed subpaths. (3.0.0) — [release notes](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v3.0.0)
- The minimum supported Node.js version is now >=22.15.0; Node.js 18 and 20 are no longer supported. (3.0.0) — [release notes](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v3.0.0)
- The browser field in package.json is replaced with #platform subpath imports; resolvers with the node condition load the Node.js build and others load the browser build. (3.0.0) — [release notes](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v3.0.0)

### Fixes and other changes

- The ESM build resolves through the default export condition, allowing resolvers that activate neither import nor require to find an entry point. (3.0.0) — [release notes](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v3.0.0)