Releases: cloudflare/next-on-pages
@cloudflare/[email protected]
Patch Changes
- ea73acc: fix variables not getting recorded correctly in
next-dev
@cloudflare/[email protected]
Patch Changes
- f07ea9b: Update the
next-dev
'ssetupDevBindings
API and remove the module's__experimental__
prefix
[email protected]
Patch Changes
-
ed9a4ac: remove the no-longer-necessary
no-app-not-found-runtime
rule in a backward compatible manner -
72426c2: update
no-unsupported-configs
with new configs optionsin the
no-unsupported-configs
rule handle the following new options:- logging
- optimizePackageImports
- ppr (Partial Prerendering)
- serverActions
@cloudflare/[email protected]
Patch Changes
-
a4efc7b: ignore invalid
_error
functions in the App routerIn the App router, error boundaries are implemented as client components (see: https://nextjs.org/docs/app/api-reference/file-conventions/error),
meaning that they should not produce server side logic.The Vercel build process can however generate
_error.func
lambdas (as they are useful in the
Vercel network I'd assume), through experimentation we've seen that those do not seem to be
necessary when building the application with next-on-pages so they should be safe to ignore.The changes here make such invalid
_error.func
lambdas (if present) ignored (as they would otherwise
cause the next-on-pages build process to fail) -
352bf4b: Make route matching check handle better trailing slashes
Currently having
trailingSlash
set totrue
in thenext.config.js
file
results in some routes not being correctly handled, this fix addresses such
issue
[email protected]
@cloudflare/[email protected]
Patch Changes
-
8fe72f1: make CLI arguments parsing more flexible
prior to this change the CLI arguments parsing was not too flexible and forced a specific style
For instance the only way to provide an argument for the
outdir
option was to pass it using=
as in:-o=./my-dir
or
--outdir=./my-dir
these changes make the CLI arguments parsing more flexible and don't enforce a specific style
(--outdir ./my-dir
now also works as you'd expect it to) -
20d0e0d: Fix
_not-found
functions only for applications using the App RouterIn #418 we introduced a workaround
that would delete invalid (nodejs)_not-found
functions during the build processAlthough the workaround is valid for applications using the App Router it is not
for applications only using the Pages Router, so make sure that it is only applied
when the former is used
[email protected]
@cloudflare/[email protected]
Patch Changes
-
61d0a2f: print warning in case developers are using a different package manager to run @cloudflare/next-on-pages
-
1e73555: Fix route intercepts causing 404s for the non-intercepted route.
-
1e73555: Fix route intercept modals not getting all the parameters for a route.
-
b7f9225: improve unhelpful error message (so that instead of
[object Object]
it prints the actual error message) -
bc216b4: Improved support for newer version of Next.js with the suspense cache through trying to handle soft/implicit tags properly
-
8ece962: fix external middleware rewrites
Currently Middleware rewrites (
NextResponse.rewrite()
) assume that the rewrite destination
is on the same host as the application, meaning that the following operations would work as intended:NextResponse.rewrite(new URL('/rewrite-dest', request.url));
while something like this would not:
return NextResponse.rewrite( new URL('https://my-customer-rewrite-site.come/rewrite-dest', request.url), );
Remove such assumption and allow such external rewrites to take place (as they do on Vercel)
-
bc216b4: Fix old version of Next.js not updating a cache entry properly due to not receving the correct shape they expected.
@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.