Releases
7 versions from Oct 12 to Oct 25, 2026. 2 MINOR releases and 4 PATCH releases came after the first release.
Each mark is one version, on a time axis in UTC. Select a mark to show its changes.
- MINOR: new features (before 1.0.0, also a change of the API)
- PATCH: fixes and small additions
- The first release
2 changes in 1 package. The changes with the most packages come first.
The default of
propagateTraceHeaderCorsUrlsis[]: the fetch and XHR instrumentations add the trace headers (traceparent) only to the requests to the origin of the page, as OpenTelemetry does.To keep the trace of your own API on another origin, give its origin:
init({ propagateTraceHeaderCorsUrls: [/^https:\/\/api\.example\.com\//] }).
3 changes in 1 package. The changes with the most packages come first.
startNodeTelemetry(): atSIGTERMandSIGINT, a service without a listener of its own now ends after the flush.The
shutdown()ofstartNodeTelemetry(): a second call waits for the flush of the first call.The documentation of the option
envtells that the SDK reads its exporter settings fromprocess.env.
1 change in 1 package. The changes with the most packages come first.
The package has the MIT license: the file
LICENSEand the fieldlicenseinpackage.json.
1 change in 1 package. The changes with the most packages come first.
runInRemoteTrace()in each entry: it runs the apply of a remote change in a consumer span whose parent is thetraceparentof the message.
4 changes in 1 package. The changes with the most packages come first.
createTraceEcho()andoutgoingTraceparent()in@mark1russell7/otel-ts/node: they carry the trace of a write to its echo from a change stream or a queue.The entry
@mark1russell7/otel-ts/node/testing:startStubCollector(), a stand-in OTLP collector for a CI check of the spans of a service.The entry
@mark1russell7/otel-ts/node:startNodeTelemetry()starts OpenTelemetry in a Node.js service.The optional peer dependency
@opentelemetry/sdk-node.
10 changes in 1 package. The changes with the most packages come first.
@mark1russell7/otel-tsdoes not load zone.js.@mark1russell7/otel-tskeeps the active span with async-browser-context.contextManager: "zone"is only in the new entry@mark1russell7/otel-ts/zone. zone.js and async-browser-context patch the same functions with different rules, so they cannot share a page.Each entry exports its own
OtelTsConfigandContextManagerOptiontypes, with thecontextManagervalues of the entry.The
contextManagervalue"async".The dependency
async-browser-context(^0.2.2).The entry
@mark1russell7/otel-ts/core: the same API, without a context library.The entry
@mark1russell7/otel-ts/zone: the same API, with zone.js.The type
ContextManagerName.When
@mark1russell7/otel-tsloads, the runtime of async-browser-context patchesPromise.prototype.then, the timers, the event listeners and other callback APIs.
1 change in 1 package. The changes with the most packages come first.
The first version.
Source: the CHANGELOG.md files, the git tags, the GitHub releases and npm, read when the site was built.