Pull request overview

This PR prevents a module-load TypeError in the fetch adapter by making destructuring from utils.global safe when it is undefined (as reported in #7259).

Changes:

• Add a default value (= {}) to the destructured parameter used to extract Request/Response from utils.global.
• Guard ReadableStream/TextEncoder destructuring by falling back to {} when utils.global is falsy.

No issues found across 1 file

Thanks @Jye10032. When fetch.js's top-level code runs before utils.js's default export has finished populating (a circular-import / evaluation-order quirk that bundlers like Vite can surface), utils.global reads as undefined, and the original destructure has no default, so it throws at module load before anything in axios can recover. Moving the read into factory() sidesteps that entirely; by the time factory is invoked from getFetch(), the ESM graph has settled.

Two small simplifications before this lands.

Flatten the fallback. utils.global is itself globalThis ?? self ?? window ?? global, so the only realistic case where it's undefined is the circular-import one and in that case globalThis is equally available. The ?? {} arm is unreachable in any environment that runs ESM:

const globalObject = utils.global ?? globalThis;

Drop the IIFE around Request/Response. With globalObject already in scope, the IIFE's only purpose (handling destructure-of-undefined at module load) is gone:

const { Request, Response } = globalObject;
const globalFetchAPI = { Request, Response };

Same shape going into the utils.merge.call(…, globalFetchAPI, env) below.

Optional but nice: a regression test that stubs utils.global to undefined, calls factory({}), and asserts no throw. The bundler-graph case is hard to reproduce in unit tests directly, but stubbing the module is a reasonable proxy.