Packages

@appsignal/nodejs

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

Upgrading @appsignal/nodejs From 2.2.4 to 2.2.5

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 2.2.4Newest 2.x2.4.2Latest3.9.5
  1. 2.2.4yours
  2. 2.2.5target
0
changes to make
0
advisories fixed
0
new
0
fixes
19 other lines we could not sort, mostly version bumps
  • Patch - Send the diagnose report with correct query parameters to help link the report to the app and organization on AppSignal.com.

    2.2.5
  • Patch - The AppSignal config is not considered valid anymore when the apiKey config option is not set.

    2.2.5
  • Patch - Print the extension installation dependencies and flags in the diagnose report output.

    2.2.5
  • Patch - Add information about the sources of each configuration value in the output of the diagnose report.

    2.2.5
  • Patch - Include the sources of each configuration value in the diagnose report that is sent to AppSignal.com.

    2.2.5
  • Patch - Standardize diagnose validation failure message. Explain the diagnose request failed and why.

    2.2.5
  • Patch - Diagnose report config opts are now printed in camel case format, matching how the configuration options are provided to the Appsignal object

    2.2.5
  • Patch - Print deprecation message when passing a filename to logPath config option. This was already deprecated. Now it also prints a warning message on app start.

    2.2.5
  • Patch - The AppSignal client is stored on the global object as to make access easier for AppSignal developers.

    2.2.5
  • Patch - Fix TypeScript compatibility for global object augmentation.

    2.2.5

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.