Wirestack
E2B JavaScript SDK 2.56.0 on October 13, 2026 requires Node.js 22.19.0 and removes the in-flight request cap
e2b 2.56.0 needs Node.js 22.19.0 or newer, drops Node.js 20 and removes the three *_INFLIGHT_REQUESTS env variables.
Your keys
0 of 1 ready
Create each key on its own page, paste it below, then copy the finished lines into your project's .env file. What you paste stays in this tab. It is never sent to Wirestack or saved.
- E2B API keyE2B_API_KEYGet key
Sign in to the E2B dashboard, open the keys tab and copy your API key. It starts with e2b_.
What you get
On October 13, 2026 E2B released the JavaScript SDK e2b@2.56.0. It requires Node.js 22.19.0 or newer. Node.js 20 is no longer supported. The SDK now depends on undici@^8 only, and undici 7 is dropped.
The release notes list a breaking change. The SDK's in-flight request cap is gone, along with the E2B_API_INFLIGHT_REQUESTS, E2B_ENVD_INFLIGHT_REQUESTS and E2B_ENVD_RPC_INFLIGHT_REQUESTS environment variables. Concurrency is now governed by undici's connection pools, set with E2B_API_CONNECTIONS and E2B_ENVD_RPC_CONNECTIONS. The notes say undici 8 honors the server's HTTP/2 concurrent stream limit and opens more connections when one is full.
Later, on October 20, 2026, e2b@2.58.0 added streamInput for commands and PTY.
Prerequisites
Steps
- Check the Node.js version on your servers, CI and serverless runtime before upgrading.
- Upgrade the
e2bpackage to 2.56.0 or later. - Remove any
*_INFLIGHT_REQUESTSvariables from your environment. - If you tuned concurrency, set
E2B_API_CONNECTIONSorE2B_ENVD_RPC_CONNECTIONSinstead, following the official docs.
Test it
Create a sandbox, run one command and close it on the upgraded SDK. Then start several sandboxes at once and check none fail.
Not confirmed
- Default values for the two connection pool variables.
- Whether the Python SDK has a similar concurrency change.
- How long older SDK versions keep working.