Packages

@appsignal/nodejs

3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed

Upgrading @appsignal/nodejs From 2.3.1 to 2.3.2

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 2.3.1Newest 2.x2.4.2Latest3.9.5
  1. 2.3.1yours
  2. 2.3.2target
3
changes to make
0
advisories fixed
0
new
2
fixes

Before you upgrade

Tick each one off as you go
  • Breaking2.3.2
  • Breaking2.3.2
  • Breaking2.3.2

Release by release

  1. 2.3.2

    Migration needed15 Feb 20222 fixes
    • Breaking

      Patch - Remove the private function Span.toJSON. This wasn't previously marked as private, but it was.

    • Breaking

      Patch - Do not ship the extension install script test files in the published package. Reduces the package size a tiny bit.

    • Breaking

      Patch - Remove the unused experimental module.

    • Fixed

      Patch - Show errors in loading the extension when the @appsignal/nodejs module is required.

    • Fixed

      Patch - The minutely probes are now stopped when Appsignal.stop() is called. This fixes an issue where Jest tests would warn about asynchronous operations that remain pending after the tests.

3 other lines we could not sort, mostly version bumps
  • Patch - Update the expected Span type in ScopeManager to Span from the @appsignal/nodejs package, rather than the NodeSpan from the @appsignal/types package. The type definition is the same, but now all Span types used by the Node.js integration are defined in the @appsigna/nodejs package.

    2.3.2
  • Patch - Improve memory usage when extension is not initialized. It will no longer initialize a new empty Tracer object when the extension is not loaded or AppSignal is not active.

    2.3.2
  • Patch - Update @appsignal/types dependency to 3.0.0.

    2.3.2

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.