voyagi/bumpwarden-demo-app / node-fetch

node-fetch 2.6.7 to 3.3.2

Scored 58 of 100, which is caution. Every factor below is computed from a source you can open, and the sum decides the band. Nothing here is a judgement call.

Where this sits

The same axis as the queue, so this bump's place in the run is legible.

body-parser 50

node-fetch 58

express 62

chalk 71

glob 87

Machine explanation, not verdict

Upgrade node-fetch to v3.3.2: timeout and size options dropped

Upgrading node-fetch from v2.6.7 to v3.3.2 is a major version bump. In node-fetch v3, the timeout and size options are no longer supported. We could not determine other breaking changes (such as ESM-only module requirements) from the provided release notes because they only cover the v3.3.2 patch release.

The timeout option is no longer supported in node-fetch v3.
The size option is no longer supported in node-fetch v3.

lib/upstream.js:11 uses timeout

"timeout: 5000," https://github.com/node-fetch/node-fetch/releases/tag/v3.3.2

lib/upstream.js:12 uses size

"size: 512 * 1024," https://github.com/node-fetch/node-fetch/releases/tag/v3.3.2

Migration

Replace the timeout option with an AbortSignal from an AbortController.
Replace the size option by limiting the response stream size manually.

Confidence high. Model gemini-3.5-flash. 2 of 2 claims matched a call site the mechanical matcher also found. None were dropped. Some inputs were truncated to fit the token budget.

Provenance