@appsignal/nodejs
3.9.5 · 11 Nov 2026MIT24.2k / weekRepositoryHomepagenpmAtom feed
Upgrading @appsignal/nodejs From 1.0.4 to 1.3.2
12 releases in betweenevery note read
Reading releases, release notes and advisories…
Release by release
1.2.4 – 1.3.26 releases, nothing new or fixed in the notes
- Fixed
Handle all non-dynamic paths as static routes in Next.js. PR #383
- Fixed
Fixes for data handling PR #385
- Fixed
- Fixed
Fix musl target and override reporting. PR #374
- Fixed
- Fixed
Don't break diagnose when agent isn't loaded
- Fixed
- New
Add minutely probe for collecting heap stats
- New
- Fixed
Fix memory leak when creating child spans by passing around span reference instead of id strings
- Fixed
- New
Allow spans to be created with a startTime
- New
19 other lines we could not sort, mostly version bumps
- 1.3.2
Patch - Update @appsignal/nodejs-ext dependency to 1.2.9.
- 1.3.1
Patch - Update @appsignal/nodejs-ext dependency to 1.2.8.
- 1.3.0
Minor - Format and print the diagnose report in a human-readable format.
- 1.3.0
Patch - Fix the log path reported when running the diagnose command to include the filename.
- 1.3.0
Patch - Limit the
appsignal.logfile size in diagnose report. It will only send the last 2MiB of the file. This prevents the diagnose report from sending too much data that it gets rejected by the server. - 1.3.0
Patch - Fix the validation of Push API key in the diagnose report. It would always print "valid" even if the key was not set or invalid.
- 1.3.0
Patch - Update @appsignal/nodejs-ext dependency to 1.2.7.
- 1.2.6
Patch - Update @appsignal/nodejs-ext dependency to 1.2.6.
- 1.2.5
Patch - Package release.
- 1.2.5
Patch - Update @appsignal/nodejs-ext dependency to 1.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.