fetch
Found in 13 packages: deno, vercel-cli, vercel-functions, next-js, clerk, sveltekit, turborepo, bun, axios, node-js, payload-cms, angular, cloudflare-workers
deno(6 releases)
v2.9.6This release includes numerous bug fixes across various modules, including desktop, fetch, http, node, npm, and web. It also introduces performance improvements in the core and web modules.
v2.5.7This patch release focuses heavily on bug fixes across compilation, bundling, and Node compatibility, particularly addressing issues related to Intel Mac builds and crypto operations.
v2.6.2Deno 2.6.2 introduces an unstable sandbox subcommand and provides numerous bug fixes across Node.js compatibility, workspace handling, and the inspector.
v2.3.6Deno 2.3.6 introduces an esbuild-backed bundler and a new deploy subcommand under unstable flags, alongside extensive fixes for Node.js compatibility and vsock socket support.
v2.3.3Deno 2.3.3 is a patch release fixing ambient module checks and formatting regressions, following 2.3.2 which introduced unix socket fetch support, custom DNS resolvers, and extensive Node.js polyfill improvements.
v2.2.4Version 2.2.4 introduces OpenTelemetry span context propagators and tracing for node:http.request, alongside numerous fixes for npm dependency resolution, LSP stability, and CJS/ESM interoperability.
vercel-cli(8 releases)
@vercel/client@18.0.0BreakingMigrated `@vercel/client` and `@vercel/build-utils` from `node-fetch` to native `fetch`, removing `url.parse()` usage and addressing a Node 24 deprecation warning. This change includes a breaking change in how HTTP agents are handled.
@vercel/build-utils@13.33.1BreakingMigrated `@vercel/client` and `@vercel/build-utils` from `node-fetch` to native `fetch`, removing `url.parse()` usage and addressing a Node 24 deprecation warning. This change includes a breaking change in how HTTP agents are handled.
@vercel/go@3.4.3This patch release addresses a naming conflict by renaming the 'fetch' import from 'node-fetch' to 'nodeFetch'.
@vercel/next@4.15.35This patch release includes a renaming change for imports from the 'node-fetch' library.
@vercel/static-build@2.8.42This patch release primarily addresses an internal naming conflict by renaming 'fetch' to 'nodeFetch' when imported from 'node-fetch' and updates a dependency.
@vercel/client@17.2.48This patch release renames the 'fetch' function to 'fetchApi' and updates several internal dependencies, including @vercel/routing-utils and @vercel/build-utils.
@vercel/node@5.6.8This patch release includes dependency updates and a necessary renaming of an import from node-fetch.
@vercel/frameworks@3.19.1This patch release includes a renaming change for imports from node-fetch to avoid potential conflicts.
vercel-functions(1 releases)
next-js(11 releases)
v16.3.0-canary.20This release focuses heavily on Turbopack improvements, error surfacing in development, and various bug fixes across routing, caching, and server actions. A configuration flag, `partialFallbacks`, has been removed.
v16.0.4BreakingThis release backports critical bug fixes related to middleware file naming, fetch error handling, and Turbopack NAPI configurations.
v15.4.2-canary.47BreakingThis release includes an internal React upgrade, several Turbopack optimizations and bug fixes, and improvements to fetch logging and typed route validation.
v15.4.0-canary.104This release focuses on Turbopack performance optimizations, bug fixes for scope hoisting, and enhancements to the segment explorer and devtools. Key improvements include MDX extension support in Turbopack and refined fetch documentation.
v15.4.0-canary.82This release introduces performance optimizations for Turbopack and Rspack, including a two-phase static generation for dynamicIO and native SWC function implementation. It also addresses config caching bugs and documentation errors.
v15.4.0-canary.42This release introduces server-only constant definitions via compiler.defineServer and improves Turbopack performance tracking and cache limit visibility. It also includes internal optimizations for rule matching and updates to the release automation process.
v15.4.0-canary.41This release introduces server-only constant definitions via compiler.defineServer and improves Turbopack performance logging and fetch cache visibility. It also synchronizes versioning between the core package and its SWC binaries.
v15.4.0-canary.19This release introduces the afterProductionCompile build hook and improves production debugging with codeframes in sourcemaps. It also includes significant internal refactoring and performance optimizations for Turbopack.
v15.3.1-canary.12This release focuses on core metadata rendering improvements, AMP bundler fixes, and significant documentation restructuring, including moving the Production Checklist to Guides.
v15.2.0-canary.61BreakingThis release focuses on dev-overlay improvements, accessibility, and the removal of the experimental reactOwnerStack flag. It also introduces a restriction on using rootParams within cache scopes.
v15.1.5This release backports several critical bug fixes related to revalidation, metadata handling, and fetch lock stability. It is a maintenance update that does not include pending features from the canary branch.
clerk(2 releases)
@clerk/tanstack-react-start@1.1.8BreakingThis patch fixes request cloning and outbound fetch operations by omitting cross-realm AbortSignal to ensure compatibility with Node 24's stricter fetch signal checks. Dependencies were also updated across several Clerk packages.
@clerk/react-router@3.1.8BreakingThis patch release fixes a critical bug related to Request cloning and outbound fetch when using Node 24, caused by stricter AbortSignal checks in undici. Dependencies were also updated across several Clerk packages.
sveltekit(6 releases)
@sveltejs/kit@2.51.0This release introduces scroll position tracking in navigation callbacks and improves CSP compatibility for hydration. Several bugs related to fetching, error handling, and tsconfig generation have also been resolved.
@sveltejs/kit@2.45.0This release introduces implicit ID setting for form objects via form.for(id) and resolves a warning issue when using fetch within remote functions.
@sveltejs/kit@2.34.0This release introduces dynamic environment variable access during prerendering and includes several bug fixes related to fetch response headers, load data serialization, and asset handling.
@sveltejs/adapter-vercel@5.10.0This release introduces the use of the web standard fetch export and updates the @sveltejs/kit dependency to version 2.32.0.
@sveltejs/kit@2.32.0This release introduces base64 inlining for fetch response streams during page load and improves error reporting for experimental remote functions.
@sveltejs/kit@2.28.0This release introduces RouteId and RouteParams to the NavigationTarget interface and adds a pending property to forms and commands, alongside several fixes for prerendering and caching.
turborepo(1 releases)
bun(1 releases)
axios(2 releases)
node-js(5 releases)
v22.21.0This release introduces built-in proxy support for fetch and http/https requests via environment variables, adds a new callback for HTTP upgrade control, and stabilizes .env file support.
v18.20.6This security release addresses three medium-severity vulnerabilities (CVE-2025-23085, CVE-2025-23084, CVE-2025-22150) involving HTTP2 memory leaks, Windows path traversal, and undici fetch randomness.
v20.18.2BreakingThis security release addresses several vulnerabilities including a high-severity issue in the Permission Model, path traversal on Windows, and memory leaks in HTTP/2.
v22.13.1BreakingThis security release addresses critical vulnerabilities including a path traversal on Windows, an HTTP/2 memory leak, and unauthorized InternalWorker access when the permission model is active.
v23.6.1BreakingSecurity release addressing multiple CVEs including path traversal on Windows, HTTP/2 memory leaks, and permission model bypasses.
payload-cms(1 releases)
angular(1 releases)
cloudflare-workers(4 releases)
miniflare@3.20250408.2This patch release focuses on fixing issues related to the stripping of the CF-Connecting-IP header during outbound requests in Miniflare and ensuring the fetch proxy message port is correctly started.
wrangler@3.114.9This patch release focuses on bug fixes, including resolving type mismatches, improving R2 validation, and addressing issues related to header stripping in local development environments. Dependencies, specifically miniflare, have also been updated.
wrangler@4.15.1This patch release addresses an unenv version mismatch and includes a temporary fix to strip the CF-Connecting-IP header during local development to mitigate a Workerd regression.
miniflare@4.20250508.1This patch fixes a regression in local development by temporarily adjusting how the `CF-Connecting-IP` header is handled within the `fetch` API during `wrangler dev` sessions.
Track Symbol Changes
Use the Change8 MCP server or GitHub Action to get notified when fetch changes.
Learn More