@appsignal/nodejs
3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed
2.4.2 is the newest release of 2.x.
In short
19 changed
Release note
Patch - Send the diagnose report with correct query parameters to help link the report to the app and organization on AppSignal.com.
Patch - The AppSignal config is not considered valid anymore when the apiKey config option is not set.
Patch - Print the extension installation dependencies and flags in the diagnose report output.
Patch - Add information about the sources of each configuration value in the output of the diagnose report.
Patch - Include the sources of each configuration value in the diagnose report that is sent to AppSignal.com.
Patch - Standardize diagnose validation failure message. Explain the diagnose request failed and why.
Patch - Diagnose report config opts are now printed in camel case format,
matching how the configuration options are provided to theAppsignalobjectPatch - Print deprecation message when passing a filename to
logPathconfig option.
This was already deprecated. Now it also prints a warning message on app start.Patch - The AppSignal client is stored on the global object as to make
access easier for AppSignal developers.Patch - Fix TypeScript compatibility for global object augmentation.
Patch - Add
filterParametersandfilterSessionDataoptions to filter out specific parameter keys or session data keys. Previously only the (undocumented)filterDataKeysconfig option was available to filter out all kinds of sample data.Patch - Rename the
apiKeyoption topushApiKeyto match other AppSignal integrations. IfapiKeyis set it will automatically setpushApiKey. TheapiKeyoption will be removed in the next major version of this package.Patch - Default log output to app STDOUT on Heroku dyno's. This makes the AppSignal logs available in the Heroku app's logs.
Patch - The
requestHeadersconfig option is now available. An allow list that gives the ability to define
which request headers you want to be shown in sample detail views. The default is a list of common
headers that do not include personal identifiable information.
Read more about request headers on our documentation website.Patch - Fix the diagnose's
log_dir_pathpath check. It now always checks the actual log file's parent directory, rather than the configured path. These two values may differ as the package does a permission check to see if thelogPathis writable or not.Patch - Fix writable check for paths in the diagnose report. Previously it only checked if a path was readable, not writable.
Patch - Check if the fallback log directory can be written to and print a warning if no log can be written there.
Patch - The logPath config option only allows writable paths. If the provided path is not writable,
it'll automatically change to the Operating System's temporary directory (/tmp).Patch - Update @appsignal/nodejs-ext dependency to 2.0.4.
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.