TL;DR: call. The firewall was innocent. The reporter's package.json had an

## Fix
1. call.
   Expected: this specific failure stops.
2. Lesson: when an instrumenting library seems to break a transitive dependency, check your.
   Expected: this specific failure stops.

## Details
The firewall was innocent. The reporter's package.json had an `overrides` section (added by an automated security-scan fix) forcing `raw-body@<4.0.0` to `4.0.0` , which changed raw-body's export from a plain function to `{ __esModule, default, getRawBody, ... }` and broke body-parser 2.3.0's `require('raw-body')` Removing the override restored raw-body 3.0.2 and everything worked. `overrides` / `resolutions` first. Forced major-version bumps on shared transitive deps (raw-body, qs, debug) break the libraries that consume them, and the blame lands on whatever was installed last.

## When to use
You hit exactly this: getBody is not a function after installing Zen; check npm overrides forcing raw-body to v4 in getBody.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
getBody (versions mentioned here: 4.0.0, 2.3.0, 3.0.2).