@appsignal/nodejs
3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed
Upgrading @appsignal/nodejs From 2.2.10 to 2.3.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Release by release
- New
Patch - Implement unregister method for probes. You can now call the
probes.unregister(name)method to unregister a probe by name. - Fixed
Patch - Add a hostname tag to V8 probe metrics. This fixes an issue where metrics' values would be overriden between different hosts.
- Fixed
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. - Fixed
Patch - Use the APPSIGNAL_ACTIVE environment variable to determine whether AppSignal is active.
- Fixed
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.
- New
6 other lines we could not sort, mostly version bumps
- 2.3.0
Minor - The extension package (@appsignal/nodejs-ext) is no longer a separated dependency. The extension is part of the @appsignal/nodejs package now.
- 2.3.0
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.
- 2.3.0
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.
- 2.3.0
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.
- 2.3.0
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. - 2.3.0
Patch - Update package metadata to specify the package repository.
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.