Release/v12.139.0

[joeyzhao2018]

The datadog-lambda-js/package.json is not included in our layers, because the layer build only copies dist there in Dockerfile (line 15).

What changed in dd-trace@5.105.0 is the hook wrapper behavior:

moduleVersion ||= getVersion(moduleBaseDir)

getVersion() calls requirePackageJson(moduleBaseDir, module). For this layer, moduleBaseDir is effectively:
/opt/nodejs/node_modules/datadog-lambda-js

1. MetricsListener.createProcessor() calls require("./api") in src/metrics/listener.ts (line 146).
2. dd-trace’s require hook sees this as an internal file under the instrumented package datadog-lambda-js. Before letting the lambda hook decide whether to patch it, dd-trace@5.105.0 tries to read datadog-lambda-js/package.json, which fails.
3. The hook returns undefined. Therefore require("./api") becomes undefined, and destructuring { APIClient } throws.

dd-trace@5.93.0 did not care in this path. Its hook wrapper did not try to read the target package’s package.json before returning module exports. So for datadog-lambda-js/metrics/api.js it just passed the real module exports through