You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-12-23T22:13:28.217Z undefined ERROR Uncaught Exception
{
"errorType": "TypeError",
"errorMessage": "hooks[payload.package] is not a function",
"stack": [
"TypeError: hooks[payload.package] is not a function",
" at /opt/nodejs/node_modules/dd-trace/packages/datadog-instrumentations/src/helpers/bundler-register.js:31:27",
" at Channel.publish (node:diagnostics_channel:143:9)",
" at ../../node_modules/express/node_modules/qs/lib/index.js (/node_modules/express/node_modules/qs/lib/index.js:26:12)",
" at __require3 (file:///var/task/functions/src/lambdas/api.mjs:21:50)",
" at <anonymous> (/node_modules/express/lib/middleware/query.js:19:10)",
" at ../../node_modules/express/lib/middleware/query.js (/node_modules/express/lib/middleware/query.js:51:7)",
" at __require3 (file:///var/task/functions/src/lambdas/api.mjs:21:50)",
" at ../../node_modules/express/lib/application.js (/node_modules/express/lib/application.js:20:13)",
" at __require3 (file:///var/task/functions/src/lambdas/api.mjs:21:50)",
" at ../../node_modules/express/lib/express.js (/node_modules/express/lib/express.js:18:13)"
]
}
The code is packaged using esbuild plugin.
The issue seems be missing qs hook when its trying to register instrument for express v4.
It looks like qs hook as removed as part of this change to support express v5
Tracer Version(s)
4.53.0
Node.js Version(s)
22
Bug Report
I got an error when updated dd-trace for lambda:
The code is packaged using esbuild plugin.
The issue seems be missing qs hook when its trying to register instrument for express v4.
It looks like qs hook as removed as part of this change to support express v5
#4913
Packaged code generated by esbuild plugin
Reproduction Code
No response
Error Logs
No response
Tracer Config
No response
Operating System
No response
Bundling
ESBuild
The text was updated successfully, but these errors were encountered: