Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.com/pages/framework-gu
Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/supported-features/
Dyeah I saw is not supported, but didnt expect it either to be officially listed considering it's so new
FWell, then try out and find out?
Dye I will probably do, just trying 14 for now. Then will see
FThere are some neat things is 15, but I think I'll wait until React 19 is out
DI was using canary already for some other project I have on remix and was thinking giving it a shot
Dis normal that my deploy appear on the pages.dev subdomain but not on the linked domain yet (linked domain appear as active already on the pages dashboard of cloudflare)
FNot tried pages yet, but for simple static asset only worker I know this works to deploy a static website ->
Dyeah specially canary, "use cache" looks dope
DSomething is off with my deploy It only works when I have the log streaming enabled o.O
D
HMight be hard for me to phrase it for you (it means that note would include a statement about where those products are heading in terms of support - which is usually something that triggers internal discussions around the phrasings 
). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788
"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does
). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does
GitHub
Summary
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...
Hhttps://github.com/cloudflare/cloudflare-docs/pull/17788 You can help phrase it better (or completely different) by commenting on the PR I did now.
D@fry69 lol I forgot I used next15 xD
Dguess that's the issue
NI did but i'm having errors due to some static routes not being able to be build with next on pages
FCloudflare asked me to export const runtime = "edge" in order to run my api routes, and after adding them it still won't build and gives the same errors:
Fnot the vencord emoji
FAWS Amplify seems to solve this issue
FWhy are pages needing a runtime
FThey're not even routes
F
JYes they are
WQQ: How to use
crypto in next.js on workers? I found if I use edge runtime, cryptoX509Certificate would be available
BHey everyone, I have a headless WordPress setup I'm deploying to pages. I'm trying to figure out how to add a hook to my account that is using
Anyways, how can I connect my github so that when branched ar emerged into main, it deploys
how can I add a hook to my account so everytime I make a new published post, it builds?
Thanks in advance!
next-on-pageswrangler.tomlAnyways, how can I connect my github so that when branched ar emerged into main, it deploys
how can I add a hook to my account so everytime I make a new published post, it builds?
Thanks in advance!
FLast I checked WordPress is written in PHP, Cloudflare Pages does not support running PHP, so you can use Cloudflare only as front end for where ever you host your PHP site. Next on Pages refers to Next.js
Or am I missing something?
Or am I missing something?
BYeha sorry, I'm bad at explaining. I'm using
However, I don't see a way to add hooks to my pages project using
@cloudflare/next-on-pagesHowever, I don't see a way to add hooks to my pages project using
@cloudflare/next-on-pages
IFor people interested in
https://nextjs.org/docs/canary/app/api-reference/functions/unstable_after
https://gist.github.com/ItsWendell/2413b1932d365ee6b3edccef879c589d
unstable_after support with next-on-pages, it just required waitUntil which I managed to inject into it:https://nextjs.org/docs/canary/app/api-reference/functions/unstable_after
https://gist.github.com/ItsWendell/2413b1932d365ee6b3edccef879c589d
KI have a question. I will start a new personal nextjs project, my plan was not use nextjs as a backend, instead I would create an API with workers and bun, my question is, nextjs hosted on cloudflare when I use some server side function to fetching some date from a bun api hosted in cloudflare workers too, is it redundant? Because I don't know if server side functions on nextjs with next-on-pages are the same as a bun API with workers. I don't know if in this way I was making something like double requests that would like reduce the free tier from Cloudflare
EMakes sense as open next will get support from multiple orgs, and I think the long term direction at cloudflare is to combine workers/pages into one product anyway
Thanks for the heads up, I'm just going to chill on my current working versions and I'll move over when things stabilise.
Thanks for the heads up, I'm just going to chill on my current working versions and I'll move over when things stabilise.
VHey,
We have a PR up to support middleware on @opennextjs/cloudflare, check the details at https://discordapp.com/channels/1283128968140161065/1288871672035803236/1301446458352074772
We have a PR up to support middleware on @opennextjs/cloudflare, check the details at https://discordapp.com/channels/1283128968140161065/1288871672035803236/1301446458352074772
FCan't check out, it links to another Discord (
# unknown). Can you link the PR on GitHub for context?
MAre there any other benefits of migrating from next-on-pages to opennextjs besides being able to use Node.js runtime, like performance, responsiveness?
RI’de just like to confirm next on pages can do SSR but not SSG correct?
JYou can do SSR and SSG, but not ISR
JLong-term support will be for the OpenNext one, and it'll enable better compatibility with Next.js features. next-on-pages will eventually be phased out once the OpenNext adaptor is in a good place.
KI'm about to start a Nextjs project and I want to host it on Cloudflare, but I need to know what in the NextJs app is charged by workers ? The rendered page is charged as one request or the fetch functions is charged as one request?
FStatic assets do not get charged, functions count as workers (in fact they are workers).
Kso basically fetch functions are charged right?
FNot every fetch call of course, but the whole function that calls fetch() must run inside a dressed up worker, that counts as one.
Kthank you, I didn't know about that
RI am getting an error with dynamic routes that generateStaticParams… I believe it was working before next 15 … So you’re saying that generateStaticParams should not throw an error?
Specifically starts with next@15.0.0-canary.175 and up.
Edge + generateStaticParams not allowed.
Specifically starts with next@15.0.0-canary.175 and up.
Edge + generateStaticParams not allowed.
BWill there be a migration guide from next on pages to opennext?
JNext.js 15 hasn't been tested with it so may have issues
BThanks!
NHi everyone. So I have a NextJS app (<15.0.0) and was trying to deploy to pages. My has both server and client functions and is still relatively small. While trying to deploy I see the files in /.next/cache are larger than the 25mb limit. Tried to troubleshoot to optimize where I can (don't have many static assets and they're small). Build direct was set to /.next and npm run build as the command. Am I doing something wrong or is it plainly a matter of refactoring everything to use Cloudflare workers?
NI'm still in early stages of Dev and while I have been deploying onto my local server and serving it up that way, thought it would be convenient to test out Pages instead