Releases: cloudflare/next-on-pages
@cloudflare/[email protected]
Minor Changes
-
888ae85: Add support for using a KV to implement the Suspense Cache via naming convention
With this change users can have their suspense cache implemented via a KV binding, in order to
opt-in to such implementation they simply need to make sure that their application has a KV binding
named__NEXT_ON_PAGES__KV_SUSPENSE_CACHE
(the next-on-pages worker will pick up such
binding and use it to implement the suspense cache instead of using the default workers cache API).
Patch Changes
- f364224: Set
x-vercel-sc-host
request header for older versions of Next.js for the suspense cache. - d7b34cc: Falling back to header if cache tags are not given from fetched CachedFetchValue object. The change was introduced from Next.js 13.5+.
- dbe2c78: Update the matcher for the temp fix for a Next.js bug to match more chars.
[email protected]
@cloudflare/[email protected]
Patch Changes
- 9d5db04: Fix broken
/__index.prefetch.rsc
rewrites that were being rewritten to/__index
(and 404ing) due to to rsc suffix stripping that we do.
[email protected]
@cloudflare/[email protected]
Patch Changes
- c83d125: Temporary hotfix for
vercel/next.js#58265
so that rendering in Next.js >= 14.0.2 works. - bf57ec9: Fix prerendered
next.config.js
basePath
root infinite redirect due to Cloudflare Pages handling of/{path}/index
. - bf57ec9: Fix nested
index.rsc
routes not generating a non-index override. - 9b290cb: Output more information about the sizes of identifiers and functions, as well as all of the consumers of each identifier.
- bf57ec9: Fix the
/_not-found
invalid function hack to work withnext.config.js
basePath
. - ee237f3: Patch the fetch function inside the fetch handler, instead of in the global scope.
- bf57ec9: Fix unncessary invalid function at the root not being discarded when using
next.config.js
basePath
option.
[email protected]
@cloudflare/[email protected]
Patch Changes
- a1091b1: bump package-manager-manager to 0.2.0
@cloudflare/[email protected]
Patch Changes
- 5b44784: bump package-manager-manager to 0.1.3
[email protected]
@cloudflare/[email protected]
Minor Changes
- 2423529: Add new static error page that informs users when they forgot to set the
nodejs_compat
flag.
This should be clearer that the simple text message we've been providing previously (which is
still being used as a fallback in case the new page is not available for some reason).
Patch Changes
-
29d3041: improve routing by following more closely Vercel's routes matching logic
-
69efaa5: Reinstate the use of the package-manager-manager package introduced in #474 and temporarily removed in #475,
this fixes the bug that was caused by the package by bumping the package itself (where the bug has been fixed)
and adding appropriate catches when the package methods can throw (in case other unexpected issues arise in the
future) -
ab83858: Changes to the x-vercel-ip headers to bring their structure in line with deployments to Vercel.
-
6600d2a: fix wasms not always getting imported when necessary
Details:
when dealing with wasms that have more than 1 consumer, when we collect
the wasm imports to prepend for a specific edge funcion we're always
re-setting the array of wasm imports instead of appending them, this
causes edge functions to always only consider the last wasm
import, the changes here fix such behavior