[DavertMik]

Problem

A fresh npm install -g explorbot@0.6.0 (and npx explorbot) crashes on start:

.../@opentelemetry/otlp-transformer/dist/logs/protobuf/logs-serializer.mjs:5
import { SeverityNumber } from "@opentelemetry/api";
SyntaxError: Named export 'SeverityNumber' not found. The requested module '@opentelemetry/api' is a CommonJS module

@langfuse/otel declares @opentelemetry/exporter-trace-otlp-http as a peer (>=0.202.0 <1.0.0). Explorbot doesn't list it, so npm auto-installs the newest match: 0.300.0 (released 2026-10-20), which needs @opentelemetry/api >=1.10.0 <1.11.0. The SDK explorbot is on (sdk-node 0.208, sdk-trace-base 2.x) needs api <1.10.0. npm keeps 1.9.1, warns ERESOLVE overriding peer dependency, and the exporter fails at import.

The repo works because bun.lock pins the exporter at 0.208.0, but npm never reads bun.lock. Older releases probably break the same way on a fresh install; installs cached before Oct 20 still work.

Fix

Add "@opentelemetry/exporter-trace-otlp-http": "^0.208.0" as a direct dependency, so the peer resolves to the line the rest of the SDK is on.

bun.lock is regenerated. Besides the new entry, bun drops the nested 0.205 exporter copies it no longer needs, and adds wrap-ansi, which main's package.json already listed but the lockfile was missing.

Verification

Took the published explorbot@0.6.0 tarball, added only this dependency, and installed it with npm install --global:

	0.6.0 as published	0.6.0 + this change
ERESOLVE warnings	5	0
invalid @opentelemetry/api peers	65	0
exporter installed	0.300.0	0.208.0
explorbot --version	crashes	0.6.0

bun test tests/unit: 1746 pass, 1 fail. The failure is enables Langfuse from LANGFUSE_* env vars, which fails on main too.

Moving the whole OpenTelemetry stack to the 0.300 / api 1.10 line is the longer-term fix. This PR is the smallest change that makes a publishable release.

🤖 Generated with Claude Code