@appsignal/nodejs
3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed
Upgrading @appsignal/nodejs From 2.3.6 to 2.4.2
3 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- Fixed
Patch - Only allow open root spans to be set as root. This avoids closed root spans to be reused in child contexts.
- Fixed
Patch - Don't return closed spans in
withSpanhelper. If a closed span was given to thewitSpanhelper it would temporarily overwrite the context with a closed span that cannot be modified. Instead it will return the current active span, if any. If no span was active it will return aNoopSpan. - Fixed
Patch - Add
@opentelemetry/sdk-trace-basepackage runtime dependency. Our OpenTelemetry SpanProcessor needs this package at runtime, not just at compile time.
- Fixed
- Fixed
Patch - Do not instrument HTTP requests to the default socket.io path. This works around an issue where our HTTP instrumentation breaks socket.io's server side, causing the client side to get stuck in a connection loop.
- Fixed
Patch - Fix removing event listeners from wrapped event emitters. When using
tracer.wrapEmitterto wrap an event emitter, it was not possible to remove any listeners that were added after the event emitter was wrapped.
- Fixed
- New
Minor - Add OpenTelemetry span processor for the mysql and mysql2 packages. These are experimental integrations and require additional set up to integrate with OpenTelemetry.
- New
Patch - Add config options for disabling default instrumentation like HTTP, HTTPS, PostgreSQL (pg package) and Redis (node-redis package).
- New
Patch - Add OpenTelemetry node-redis and ioredis query sanitizers. We recommend using these sanitizers to ensure no sensitive data is sent in query statements. Add the sanitizer to the
dbStatementSerializerconfig as demonstrated below. - Fixed
Patch - Fix the
ScopeManager.active()function returning closed spans. - Fixed
Patch - Do not transfer closed spans for new async contexts in the ScopeManager. Rather than relying on
ScopeManager.active()andScopeManager.root()to make sure the span is not already closed, also make sure it's not closed when transferring spans around between async contexts.
- New
4 other lines we could not sort, mostly version bumps
- 2.4.2
Patch - Do not restore closed spans from within the
withSpanhelper. If a previously active span gets closed whilewithSpanhas another span as currently active, do not restore the closed span when the callback has finished. - 2.4.2
Patch - Do not restore root span after
withSpancallback has finished. Previously the root span was restored to the original root span before thewithSpanhelper was called. This has been changed, because thewithSpanhelper is only about changing the active span, not the root span. If a new root span has been set within awithSpanhelper callback, the root span will no longer be restored. We recommend setting a new root span before callingwithSpaninstead. - 2.4.0
Patch - Use the OpenTelemetry SpanProcessor interface to build our own SpanProcessor. We previously copied the SpanProcessor code into our package, but instead we now use the OpenTelemetry interface directly. This should make our processor match the expected type better.
- 2.4.0
Patch - Bump agent to v-0b43802.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.