basically the `setupDevPlatform` call can stay as is, what you need to change is `getRequestContext`

basically the

setupDevPlatform

setupDevPlatform

call can stay as is, what you need to change is

getRequestContext

getRequestContext

and make sure that it is not being called as part of the route initialization (e.g. don't put

getRequestContext()

getRequestContext()

to the top level of a route file, but have it part of a function that gets called when the route is actually run)

Lluna does this include next on pages?

DarioOP•3/12/24, 10:28 AM

yes, I do think so (but I could be wrong)

DDario yes, I do think so (but I could be wrong)

luna•3/12/24, 10:28 AM

if it does it doesn’t seem to be working.

Lluna if it does it doesn’t seem to be working. 😅

DarioOP•3/12/24, 10:35 AM

oh.... ok sorry, I'll have to check with the team and/or play a bit with it myself

DDario oh.... ok sorry, I'll have to check with the team and/or play a bit with it myse...

luna•3/12/24, 10:37 AM

cheers, so far i have a site using next on pages with git. i enabled it about a week ago and have done multiple deploys since. still nothing shows in the analytics ui and i don’t see anything being added to the page’s head.

i’ve disabled and re-enabled and no change.

DarioOP•3/12/24, 10:43 AM

I see, I'll have a look thanks for the info

DDario basically the `setupDevPlatform` call can stay as is, what you need to change is...

Mongy•3/12/24, 2:59 PM

Hmmmmm the

getRequestContext

getRequestContext

can't be called within an actions.ts due to edge runtime requirement. Gana have to find another way to populate data to a client component.

DarioOP•3/12/24, 5:49 PM

@luna I've tried and web analytics seems to be totally working with next-on-pages

DarioOP•3/12/24, 5:50 PM

do you get a bacon script in your page's body by any chance?

DarioOP•3/12/24, 5:50 PM

DarioOP•3/12/24, 5:51 PM

what about the rum http requests?

DarioOP•3/12/24, 5:51 PM

GetPsyched•3/13/24, 7:59 AM

Please make sure that all your non-static routes export the following edge runtime route segment config:

How do I know which route is this referring to?

GetPsyched•3/13/24, 7:59 AM

Got this error in the log after a successful build, but apparently I have non-static routes?

GGetPsyched > Please make sure that all your non-static routes export the following edge run...

DarioOP•3/13/24, 9:20 AM

@GetPsyched could you share a screenshot?

DDario <@534651911903772674> could you share a screenshot? 🙂

GetPsyched•3/13/24, 10:54 AM

here's a copy of the log

message.txt12.79KB

GetPsyched•3/13/24, 10:55 AM

Oh all of the routes were not able to be pushed

GetPsyched•3/13/24, 10:56 AM

My middleware already defines two possible values for

locale

locale

then why is it not static

GetPsyched•3/13/24, 10:56 AM

Okay I guess this is a problem in my project, so will keep the discussion off this server, sorry and thanks

DarioOP•3/13/24, 11:01 AM

I see

, cool hopefully you can fix the issue, otherwise please do feel free to post here and we can try to help

(opening a thread should also help not making this noisy for everyone)

seasie•3/13/24, 7:51 PM

the

persist

persist

option of

setupDevPlatform

setupDevPlatform

doesn't appear to be working as expected, unless I have it configured incorrectly

if (process.env.NODE_ENV === "development") {
    await setupDevPlatform({
        persist: "../../.wrangler/search/v3",
    })
}

if (process.env.NODE_ENV === "development") {
    await setupDevPlatform({
        persist: "../../.wrangler/search/v3",
    })
}

but it still creates and accesses data from

.wrangler/state/v3

.wrangler/state/v3

, I've tried both with and without

v3

v3

at the end of the path

FFiru my form would POST to the same URL as the page, leading to a 405 tho

Dudu•3/13/24, 8:59 PM

Heyo o/

Did you manage to solve this and if so how?

Dudu•3/13/24, 8:59 PM

I'm also getting 405 Method Not Allowed with the NextJS actions

DDudu Heyo o/ Did you manage to solve this and if so how?

Firu•3/14/24, 12:59 AM

I haven't fixed it. I migrated away from Next.js on Cloudflare Pages ):

Firu•3/14/24, 12:59 AM

i'd gladly migrate back if that issue didn't exist tho

FFiru I haven't fixed it. I migrated away from Next.js on Cloudflare Pages ):

Dudu•3/14/24, 12:15 PM

I have found a work around but now I'm getting this every time I submit the form

DDudu I have found a work around but now I'm getting this every time I submit the form

Firu•3/14/24, 12:15 PM

what's the workaround?

FFiru i tried doing `export const runtime = 'edge'` on both files and it still wouldn'...

Dudu•3/14/24, 12:16 PM

I tried this in different files until it worked

Dudu•3/14/24, 12:17 PM

In my case I have it on page.tsx

Dudu•3/14/24, 12:17 PM

Which has the component with 'use client' with the form

Meetee•3/14/24, 2:14 PM

Hi, how can I know the exact file that cause this error?

Meetee•3/14/24, 2:19 PM

I just re-run any successful deployment in the past, and the error is still there, maybe it's not the nextjs's problem

MMeetee Hi, how can I know the exact file that cause this error?

DarioOP•3/14/24, 6:03 PM

Hi @Meetee , that error message is a bit misleading... with

Functions script

Functions script

it's basically referring to all your javascript code (that gets shipped to the runtime), so this is basically saying that your application, generally doesn't fit the free tier workers size limit

DarioOP•3/14/24, 6:04 PM

If you could move to the paid plan the limit there increases to 10MiB: https://developers.cloudflare.com/workers/platform/limits/#worker-size

Cloudflare Docs

Limits · Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

oljimenez•3/15/24, 7:13 AM

Hi guys, i'm unable to make Cloudflare next-on-pages work on development using Docker. When i run the app locally it work well, but when i run the same app on Docker environment it just crash.

Github repo for reproduction. https://github.com/oljimenez/cloudflare-app

GitHub

GitHub - oljimenez/cloudflare-app

Contribute to oljimenez/cloudflare-app development by creating an account on GitHub.

zapalona_swieczka•3/15/24, 5:15 PM

I'm working on testing migrating next project to cf pages, seeing some issues here and there I wonder if anyone launched productionally some more complex site, not just static pages (like ecommerce frontend)?

thanhle•3/15/24, 7:41 PM

how do I get support with image optimization for cloudflare pages use next-on-pages in nextjs

thanhle•3/16/24, 3:21 AM

how do i set up the prisma with next-on-pages applicataion?

Nooc•3/16/24, 3:33 AM

Is anybody knows how to access Cloudflare Environments (KV, Workers AI etc) in server actions?

Tthanhle how do I get support with image optimization for cloudflare pages use next-on-pa...

Befus•3/16/24, 8:43 AM

https://github.com/cloudflare/next-on-pages/blob/60eb0aef9d7b0835204e62c167f9f0cbd5c23404/packages/next-on-pages/docs/supported.md

GitHub

next-on-pages/packages/next-on-pages/docs/supported.md at 60eb0aef9...

CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages

NNooc Is anybody knows how to access Cloudflare Environments (KV, Workers AI etc) in s...

Befus•3/16/24, 8:44 AM

https://github.com/cloudflare/next-on-pages/tree/60eb0aef9d7b0835204e62c167f9f0cbd5c23404/packages/next-on-pages#cloudflare-platform-integration

GitHub

next-on-pages/packages/next-on-pages at 60eb0aef9d7b0835204e62c167f...

CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages

Tthanhle how do I get support with image optimization for cloudflare pages use next-on-pa...

Deo Kumar•3/16/24, 3:43 PM

For image optimisation on edge runtime, you can use https://github.com/node-libraries/wasm-image-optimization

GitHub

GitHub - node-libraries/wasm-image-optimization: Optimize images wi...

Optimize images with wasm on edge runtime. Contribute to node-libraries/wasm-image-optimization development by creating an account on GitHub.

Chris (L3)•3/16/24, 7:23 PM

I've been unable to use Server Actions with next apps deployed on Cloudflare Pages. The only working solution is the one in this comment (https://community.cloudflare.com/t/next-js-server-action-error-405/601134/3), which is to set the

runtime = edge

runtime = edge

, but that nullifies static generation, right?

If I have a simple page with a form that has a Server Action, and I set the runtime to

edge

edge

that means the page will be rendered for each request, isn't that right? Am I missing something?

Chris (L3)•3/16/24, 7:24 PM

In my experience this also introduces other weird issues throughout the app that are hard to debug the more complex it gets.

Chris (L3)•3/16/24, 9:21 PM

Basically for me, if you're saying Server Actions are compatible with Cloudflare but you have to do this to your project that's very misleading. I hope I'm missing something, new to the overall Cloudflare infrastructure offering so I don't know the nitty gritty details.

Chris (L3)•3/16/24, 9:34 PM

Is there a way to keep a page statically generated, while using Server Actions? Or will that never happen on Cloudflare, it's either full static or full dynamic?

CChris (L3)Is there a way to keep a page statically generated, while using Server Actions? ...

Hello, I’m Allie!•3/16/24, 9:46 PM

As I understand, it is a limitation of Next itself. It's server expects control over serving all pages/assets, so all routes will incur functions requests, regardless of whether or not they are actually dynamic

Chris (L3)•3/16/24, 11:35 PM

Alright, so if I have a page that doesn't need hydration, doesn't have any interactive stuff, not even server actions (so not setting

runtime: edge

runtime: edge

), will that page be statically generated and served like it would be from R2/CDN basically? Or is everything run each time, even the 100% static pages. I'm trying to figure out how the NextJS bundle generation, NextJS caching, Cloudflare caching, and overall Cloudflare infra work together. Are there any resources about this I can read?

James•3/17/24, 12:37 PM

If you're using @clourflare/next-on-pages, you will incur a function invocation for every request. Your pages may be prerendered at build time and these pretended files will be served instead of doing SSR, but it still results in an invocation because requests to routes need to go through the routing system so that they can correctly match up with the right prerendered file or edge function, based on rules determined by Vercel during build.

James•3/17/24, 12:44 PM

I haven't actually investigated the 405 with server actions before, but if you're calling it from a prerendered route, i would speculate that on Vercel they bypass the prerendered route and invoke the nodejs function for action calls on static routes, which is not something we are able to do. Again, I haven't looked into it before, but that would be an initial assumption.

JJames If you're using @clourflare/next-on-pages, you will incur a function invocation ...

Chris (L3)•3/17/24, 6:08 PM

Alright, but to clarify, the message in the console at build time (whether it's in a next-on-pages or plain create-next-app) that says "enabling edge runtime disables static generation" is correct, right? The request that Cloudflare will make will be one to render the page each time, not to get it from a file bucket with pre-rendered pages (even if the page has no interactivity, but it has the

edge

edge

runtime set). Yes, I get it that it invokes a function each time no matter what, question is does the function render the static page each time, or serve the pre-rendered file.

basically the `setupDevPlatform` call can stay as is, what you need to change is `getRequestContext`

Similar Threads