NewIntegrations Node SDK
v1.15.0
Minor Changes
- ebcc7bc: A failed
safeFetchsays whether the request was sent (PO-808). When no hop of any attempt put a byte on the wire — a refused address before the lookup or at connect time, a lookup timeout, an unsendable header or URL, a credential bound to another origin, or a connection that was refused, unresolved, unreachable or timed out while connecting — the error carriesmeta.sent = false. The newmayHaveBeenSent(err)reads it, and answerstruefor everything else. Errors from the runtime stayTypeErrors with theircauseunchanged.
Patch Changes
- ebcc7bc:
safeFetchworks on Node 26 again (IN-40). It sends through undici's ownfetch, the one its guarded dispatcher belongs to, instead of the runtime's built-infetch— Node 26 refused the SDK's undici 6 dispatcher and every request failed withfetch failed. Afetcha test puts in the global's place is still called instead, so package suites that stubglobalThis.fetchkeep working, and every answer is still the runtime's ownResponse.