Alright, but to clarify, the message in the console at build time (whether it's in a next-on-pages o

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.

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

Thanks for the help James!

CChris (L3)Alright, but to clarify, the message in the console at build time (whether it's ...

James•3/17/24, 6:31 PM

Yes, if you enable the edge runtime for a route, it will always create an edge function, because Vercel don't want to support prerendered routes or ISR when someone uses the edge runtime.

When the edge runtime is enabled, it creates a function that is run at each request to SSR the route.

When not using the edge runtime for a route, it will be prerendered and served from the static assets by the router.

Chris (L3)OP•3/17/24, 8:33 PM

You're a boss, thanks!

Pepijn•3/18/24, 10:44 AM

Hi, I have a turborepo including a Next project that is deployed on CF pages. Everything works fine, but build caching says 'Skipping build output cache as it's not supported for your project'. Is this due to using turborepo? The source directory to build in is set to the app directory. Or why would the build ouput be skipped?

Pepijn•3/18/24, 10:46 AM

Also yarn v3 dependencies located in .yarn/cache are not being cached, I wanted to set the yarn cache dir to .next/cache/yarn to make it work, but due to the build output cache being skipped, that workaround is not possible.

Aalongubkin Yeah, I'll debug it more on my own (wasn't aware of the `deployment tail` trick)...

mr nooli•3/18/24, 11:10 AM

any luck with this? I'm getting this trying to run prisma & the neon driver

mr nooli•3/18/24, 11:13 AM

I believe potentially due to using a singleton pattern for the prisma connection, is there an example I can look at on how to use neon & prisma in a CF worker

Mmr nooli any luck with this? I'm getting this trying to run prisma & the neon driver

Chris (L3)OP•3/18/24, 6:42 PM

The right way of using prisma is by installing drizzle (https://orm.drizzle.team/docs/get-started-postgresql#usage-with-cloudflare-workers)

Drizzle ORM - PostgreSQL

Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.

Pat Branchaud•3/19/24, 12:30 AM

Hello! I’m about to try this, but does this setup https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/ allows next ssr functionality? In other words, is this can replace Vercel completely? Thank you

Cloudflare Docs

Full-stack deployment · Cloudflare Pages docs

Deploy a full-stack Next.js site (recommended).

James•3/19/24, 6:18 AM

Yes you can have SSR if you opt a route into the edge runtime

Mahbub Hasan Hira•3/19/24, 7:48 AM

I am trying to deploy nextjs 12 on CF. but said to add edge runtime to SSG or ISR pages like first image. I export the edge runtime as like 2nd pic but after that CF says that same error. The last image is the build config. How can I solve the error?

Mahbub Hasan Hira•3/19/24, 8:43 AM

and my nextjs version is 12.1.0

Pepijn•3/19/24, 9:40 AM

Has anyone got Sentry logging (server + client) up and running with Next on Pages using the App router?

Pepijn•3/19/24, 9:40 AM

Doesnt seem to work if I follow the sentry install wizard of their next plugin

Pepijn•3/19/24, 10:03 AM

I also have another issue with next-on-pages where sometimes the revalidateTag in a server action is returning the error: "Error: Invariant: static generation store missing in revalidateTag X"

thanhle•3/19/24, 12:47 PM

i have a question: is there any tool that can convert the code nextjs written in nodejs to cloudflare edge runtime (v8 engine) to deploy in cloudflare

James•3/19/24, 12:59 PM

Not currently

PPepijn Has anyone got Sentry logging (server + client) up and running with Next on Page...

ItsWendell•3/19/24, 9:37 PM

Also curious about this, I wanna try out vercel's open telemetry package soon, for workers people use generally ToucanJs, a sentry compatible package, but it hasn't been updated in a while. I know a while ago there was some conversation in the sentry cliënt GitHub. Keep me posted if you find a nice solution, I'll look into this in the next coming weeks too!

MMahbub Hasan Hira and my nextjs version is 12.1.0

Pat Branchaud•3/19/24, 11:52 PM

Try placing it at the very beginning of the file

Pat Branchaud•3/20/24, 5:17 PM

Does —turbo flag apply for cloudflare next-on-pages ??

Pat Branchaud•3/20/24, 10:29 PM

Another question, are the server actions functional with next-on-pages ? https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations

Data Fetching: Server Actions and Mutations | Next.js

Learn how to handle form submissions and data mutations with Next.js.

Dario•3/20/24, 11:04 PM

yes they are

Pat Branchaud•3/20/24, 11:05 PM

That’s fnice

Dario•3/20/24, 11:06 PM

although they might not work everywhere

https://github.com/cloudflare/next-on-pages/issues/679

GitHub

[🐛 Bug]: Calling server actions on a static or SSR pages returns 40...

next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020 CPU...

Dario•3/20/24, 11:06 PM

I need to investigate this

Pat Branchaud•3/20/24, 11:11 PM

I’ll try in our test setup and let you know. Don’t worry even if there are minor bugs, it is solving a lot of problems for us. Keep up the good work

Dario•3/20/24, 11:16 PM

awesome! thanks!

Dario•3/20/24, 11:17 PM

yeah please let me know, either here or by opening issues in the gh repo

Pat Branchaud•3/20/24, 11:18 PM

Do you think this setup is similar to next-on-pages in terms of performance results? https://youtu.be/ItGUt2DqNy4?si=8YqMvbv4U-xwJoRN

YouTubeJosh tried coding

A Better Way to Write APIs?

Turns out a method i found out that seemed pretty hacky to me at first because it messes with framework defaults actually works quite well. It's pretty fast, cheap, and easy to set up. Honestly there might be bugs that I haven't found yet, so please dont use this in production yet lol

-- sources for this video
hono: https://hono.dev/
cloudflare...

Dario•3/20/24, 11:28 PM

I must admit that I haven't done any proper benchmarking but I think that using next-on-pagesnext-on-pages basically makes that whole strategy mute and you get the exact same benefits as shown in that video without having to do anything nor even use hono directly in your Next.js app

Dario•3/20/24, 11:30 PM

next-on-pages basically generates a worker for you, which via lazy loading brings in and executes the minimum amount of code possible to handle a request, all done at the edge, so as long as Next.js is involved I don't think you can get much faster than using next-on-pages

Dario•3/20/24, 11:31 PM

next-on-pages is not perfect and does have it's drawbacks and issues, but performance wise in theory it should be practically the most performant way to deploy a Next.js app

Dario•3/20/24, 11:31 PM

(including the API routes of course)

Pat Branchaud•3/20/24, 11:42 PM

That’s music to my ears

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

Hello there. Is the smart placement work on next-on-pages yet?

James•3/21/24, 9:25 AM

smart placement is pretty broken with Pages in general at the moment

DDario next-on-pages is not perfect and does have it's drawbacks and issues, but perfor...

Pepijn•3/21/24, 9:34 AM

Hi Dario, could you elaborate on the existing drawbacks and issues? Just starting with next on pages and seems to run fine for us, but before making a switch from Vercel with big projects, want to know the ins-and-outs

JJames smart placement is pretty broken with Pages in general at the moment

thanhle•3/21/24, 12:48 PM

But it still works well with Workers. Is it correct?. i am planning use next-on-pages for deploy my nextjs app and use CloudFlare Workers for API route with smart placement. what do you recommend about this setup?

JJames smart placement is pretty broken with Pages in general at the moment

thanhle•3/21/24, 1:04 PM

You mean this is the Pages Functions?

juanferreras•3/21/24, 9:18 PM

we've been adopting next-on-pages recently and it's been working really, really great (kudos to Dario/James/any other contributors I might be missing!)

(on a somewhat similar note to the messages above) I did want to know if either of you had any methods to reliably profile timings in Cloudflare workers – we were surprised to see that:

const t0 = Date.now();
const data = env.KV.get(key);
const t1 = Date.now();

const t0 = Date.now();
const data = env.KV.get(key);
const t1 = Date.now();

seemed to be reporting XXX msXXX ms in lab conditions even on cache hits (where in a plain worker we see XX msXX ms_. Then we realized it wasn't KV but rather the first IO we had (and with the CF Workers security measures, we understand we could be measuring things before that I/O that just wait for the I/O to tick?)

Tthanhle But it still works well with Workers. Is it correct?. i am planning use next-on-...

James•3/22/24, 6:30 PM

I'm not sure about workers because I don't use Workers, I just know that Smart Placement can cause internal errors with Pages. You can try your setup though, I'm not sure if it only happens with Pages functions or if it also happens with static assets

Logan•3/22/24, 11:36 PM

I have a question. If we were to deploy a server side NextJS app to pages, is there a list of originating IP addresses that app would communicate with or a way to get a list of IPs from our deployment that can be whitelisted on another system we have?

LLogan I have a question. If we were to deploy a server side NextJS app to pages, is th...

JohnDotAwesome•3/23/24, 12:15 AM

Someone correct me if I'm wrong, but the IP's of outgoing requests from Workers ought to match Cloudflare's ips's https://cloudflare.com/ips but just because a request is coming from that IP doesn't mean it's legitimate traffic. There's some good info here https://news.ycombinator.com/item?id=26690388

IP Ranges | Cloudflare

This page is intended to be the definitive source of Cloudflare’s current IP ranges.

kentonv

Hi, I'm the tech lead of Cloudflare Workers.This article contains several misunderstandings.If a Cloudflare customer has configured their origin server to respond only to Cloudflare IPs, then they MUST also verify that the "Host" header on any request actually matches their domain name. If they do not verify the Host header, then anyone can sign...

Hacker News

•

4/4/21, 3:47 PM

JJohnDotAwesome Someone correct me if I'm wrong, but the IP's of outgoing requests from Workers ...

Logan•3/23/24, 12:25 AM

If that is the case, that is awesome. Will wait on any anti-confirmation.

JJames I'm not sure about workers because I don't use Workers, I just know that Smart P...

thanhle•3/23/24, 1:41 AM

thank you so much for the infor James

quisi.do•3/23/24, 9:00 AM

Just found this. I've been deploying Next SSG to Pages for a hot minute now. Is this channel for SSR? I wasn't aware of Pages offering SSR. If so, is there any documentation about this?

Qquisi.do Just found this. I've been deploying Next SSG to Pages for a hot minute now. Is ...

Hello, I’m Allie!•3/23/24, 9:20 AM

Yes, it is. next-on-pages adapts Next’s Serverless code to make it compatible with Pages

Qquisi.do Just found this. I've been deploying Next SSG to Pages for a hot minute now. Is ...

Dario•3/23/24, 11:30 AM

Yes, it's documented here

https://developers.cloudflare.com/pages/framework-guides/nextjs/
(specifically for Next.js)

Cloudflare Docs

Deploy a Next.js site · Cloudflare Pages docs

React framework for building full-stack web applications.

Pat Branchaud•3/23/24, 2:47 PM

Hey, I’m trying to find a solution for hosting with next-on-pages a full slug translation i18n (ex: fr/blogue, en/blog). Looking for a solution without the use of a middleware like amannn/next-intl does, the only viable I found right now is svobik7/next-roots copying folders on build. Any other ideas or examples your guys are aware of? 3 days of searching now and It seems complicated..

James•3/23/24, 5:08 PM

You could maybe use next.config.js rewrites, but that could end up being pretty laborious

Alright, but to clarify, the message in the console at build time (whether it's in a next-on-pages o

Similar Threads

Similar Threads

Similar Threads