@appsignal/nodejs
3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed
2.4.2 is the newest release of 2.x.
In short
1 new4 fixed6 changed
Release note
Added
Patch - Implement unregister method for probes. You can now call the
probes.unregister(name)method to unregister a probe by name.
Changed
Minor - The extension package (@appsignal/nodejs-ext) is no longer a separated dependency.
The extension is part of the @appsignal/nodejs package now.Patch - Update install report path location. The "nodejs" package now stores the install report in its own package path, with the rest of the extension files. This makes it easier to access by the diagnose report.
Patch - Improve the reporting of extension loading state in the diagnose report. Previously it would only report it as loaded when it was also running.
Patch - Change the way the extension is started. Previously it was started on initialization of the extension class (if the config was active), but now it's started by the client class.
Patch - Remove the
osandcpufields from thepackage.json. This will prevent installations from failing on unlisted CPU architectures and Operating Systems. Our extension installer script will do this check instead. The package should not fail to install when it encounters an unsupported CPU architecture or Operating System.Patch - Update package metadata to specify the package repository.
Fixed
Patch - Add a hostname tag to V8 probe metrics. This fixes an issue where metrics' values
would be overriden between different hosts.Patch - Setting
enableMinutelyProbestofalsenow disables the minutely probes
system. Custom probes will not be called when the minutely probes are
disabled. In addition, theAPPSIGNAL_ENABLE_MINUTELY_PROBESenvironment
variable can now be used to enable or disable the minutely probes.Before this change, setting
enableMinutelyProbestofalsewould not
register the default Node.js heap statistics minutely probe, but custom
probes would still be called. To opt in for the previous behaviour,
disabling only the Node.js heap statistics minutely probe without disabling
custom probes, you can use theprobes.unregister()method to unregister
the default probe:const probes = appsignal.metrics().probes(); probes.unregister("v8_stats");Patch - Use the APPSIGNAL_ACTIVE environment variable to determine whether AppSignal is active.
Patch - Fix the extension function fallbacks on installation failure. When the extension fails to install and calls are made to the not loaded functions, it will no longer throw an error.
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.