fix(js-sdk): don't return the unchanged request/response from the API logger

[KarlFredrikssonEthira]

Fixes #1986.

Problem

On Node, passing a logger makes every API call fail before the response is handled:

Error: onResponse: must return new Response() when modifying the response

On Node, the API client fetches through undici, whose Response is not globalThis.Response. createApiLogger returned the response it received from onResponse. openapi-fetch treats any returned value as a replacement, and requires it to be instanceof Response (the global class), so it throws. Under Bun and in browsers the SDK uses the global fetch, so it doesn't happen there.

Fix

The onRequest and onResponse hooks in createApiLogger now return nothing, which openapi-fetch reads as "unchanged". The logging itself is the same.

Usage

This now works on Node:

import { Sandbox } from 'e2b'

const sandbox = await Sandbox.create({ logger: console })

Tests

• New test in tests/logs.test.ts: an openapi-fetch client whose fetch returns an undici Response, with createApiLogger installed. It fails on main with the error above and passes with this change.
• pnpm run lint and pnpm run format are clean for the changed files.
• I couldn't run pnpm run typecheck fully: in my partial install, @e2b/dockerfile-utils wasn't built, so it fails in files this change doesn't touch.
• The Python SDKs don't use openapi-fetch or this middleware, so there is no equivalent change there.

Changeset: e2b patch.

🤖 Generated with Claude Code

---

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Karl Fredriksson.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[changeset-bot]

🦋 Changeset detected

Latest commit: e918f17

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
e2b	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T05:06:33.787728Z	e918f17	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[devin-ai-integration]

TASTE.md review: complies — checked T-1 (parity: Python SDKs do not use openapi-fetch middleware, so no mirror change needed), T-54 (createApiLogger stays internal, not exported from index.ts), T-69/T-70 (no public surface changed); 0 violations.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e918f17077

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep undici out of the shared browser test

When the browser matrix job runs pnpm test:browser, tests/runtimes/browser/vitest.config.mts includes every tests/**/*.test.ts and excludes tests/undici.test.ts specifically because the undici package is Node-only. This new top-level import therefore makes Vite load undici in Chromium before the test can run, causing the required browser leg (and thus SDK Tests Status) to fail during module setup. Move this regression case into the already excluded Node-only suite or construct a foreign response without statically importing undici.

Useful? React with 👍 / 👎.

[mishushakov]

Hey, please sign the CLA and read the above suggestions.