Can't check out, it links to another Discord (`# unknown`). Can you link the PR on GitHub for contex

Ffry69 Can't check out, it links to another Discord (`# unknown`). Can you link the PR ...

V

Victor Berchet•10/31/24, 7:28 AM

M

micooz•11/1/24, 3:17 AM

Are there any other benefits of migrating from next-on-pages to opennextjs besides being able to use Node.js runtime, like performance, responsiveness?

R

R in Tokyo•11/1/24, 11:03 AM

I’de just like to confirm next on pages can do SSR but not SSG correct?

RR in Tokyo I’de just like to confirm next on pages can do SSR but not SSG correct?

J

James•11/1/24, 5:57 PM

You can do SSR and SSG, but not ISR

Mmicooz Are there any other benefits of migrating from next-on-pages to opennextjs besid...

J

James•11/1/24, 5:58 PM

Long-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.

K

Kimitri•11/1/24, 6:10 PM

I'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?

KKimitri I'm about to start a Nextjs project and I want to host it on Cloudflare, but I n...

F

fry69OP•11/1/24, 6:11 PM

Static assets do not get charged, functions count as workers (in fact they are workers).

Ffry69 Static assets do not get charged, functions count as workers (in fact they are w...

K

Kimitri•11/1/24, 6:14 PM

so basically fetch functions are charged right?

KKimitri so basically fetch functions are charged right?

F

fry69OP•11/1/24, 6:15 PM

Not every fetch call of course, but the whole function that calls fetch() must run inside a dressed up worker, that counts as one.

Ffry69 Not every fetch call of course, but the whole function that calls fetch() must r...

K

Kimitri•11/1/24, 6:16 PM

thank you, I didn't know about that

JJames You can do SSR and SSG, but not ISR

R

R in Tokyo•11/1/24, 11:58 PM

I 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.

JJames Long-term support will be for the OpenNext one, and it'll enable better compatib...

B

Baran•11/2/24, 8:29 AM

Will there be a migration guide from next on pages to opennext?

RR in Tokyo I am getting an error with dynamic routes that generateStaticParams… I believe i...

J

James•11/2/24, 2:24 PM

Next.js 15 hasn't been tested with it so may have issues

BBaran Will there be a migration guide from next on pages to opennext?

J

James•11/2/24, 2:24 PM

https://opennext.js.org/cloudflare/get-started#5-remove-cloudflarenext-on-pages-if-necessary

JJames https://opennext.js.org/cloudflare/get-started#5-remove-cloudflarenext-on-pages-...

B

Baran•11/3/24, 3:16 PM

Thanks!

N

Nexorsist•11/5/24, 1:43 PM

Hi 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?

N

Nexorsist•11/5/24, 1:43 PM

I'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

B

burguês•11/5/24, 2:43 PM

Subject: Build Failure Due to Bundle Size Limit Exceeded

Hi everyone,

I'm experiencing an issue while deploying my Next.js app on Cloudflare Pages. The build fails with this error:

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Earlier in the logs, it mentions:

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

It seems my bundle size exceeds the 25 MiB limit. Here's a snippet from the build log:

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

I believe the large number of modules and functions is causing the issue. Does anyone have advice on how to reduce the bundle size or handle this situation? Or how to check bundle size?

Thanks in advance!

HHello, I’m Allie!Pages doesn’t support Crons

M

MarcusAurelius•11/5/24, 4:40 PM

Does the new worker's framework platform have support for cron ? If i have a nextjs app deployed can i add a scheduled trigger to the function ?

Does anyone know how to run a cronjob with open-next cloudflare, nextjs 15 ?

MMarcusAurelius Does the new worker's framework platform have support for cron ? If i have a nex...

H

Hello, I’m Allie!•11/5/24, 4:42 PM

Workers with Assets are also able to export a Scheduled Handler for Crons. As for whether

open-next

open-next

open-next

open-next itself supports it, I am not sure

C

Chapi•11/5/24, 5:20 PM

Hey guys

Was working on nextjs on CF pages and I always use binding on the API side now I wanted to use on server actions and it is saying

only async function are allowed to be used in use server. File

only async function are allowed to be used in use server. File

only async function are allowed to be used in use server. File

only async function are allowed to be used in use server. File but the getRequestContext method is not async I think.

Does anyone knows how to use since I kinda need the bindings to work.

B

burguês•11/5/24, 5:21 PM

Generated Pages Functions bundle size (26282201) is over the limit of 25.0 MiB
Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

How to check bundle side? How to understand which file is causing this?

CChapi Hey guys Was working on nextjs on CF pages and I always use binding on the API...

D

D Trombett•11/5/24, 10:20 PM

Remove the

export const runtime = "edge"

export const runtime = "edge"

export const runtime = "edge"

export const runtime = "edge". It is not needed in use server files

DD Trombett Remove the `export const runtime = "edge"`. It is not needed in use server files

C

Chapi•11/5/24, 10:21 PM

It is needed for any server side code. The issue is with the context which is a sync function and all server actions functions must be async

D

D Trombett•11/5/24, 10:26 PM

No it's not, the error is clearly highlighting that line. I use server actions too and can confirm that the runtime option is unavailable/not needed. Do ensure that you have it in your root layout or in single pages, tho

D

D Trombett•11/5/24, 10:27 PM

Also, about the context, you're calling

getRequestContext()

getRequestContext()

getRequestContext()

getRequestContext() inside an async function so it's totally fine

MMarcusAurelius Does the new worker's framework platform have support for cron ? If i have a nex...

J

James•11/6/24, 8:29 PM

Heya, can you open an issue on the opennext-cloudflare repo for cron support

CChapi Hey guys Was working on nextjs on CF pages and I always use binding on the API...

J

James•11/6/24, 8:30 PM

The problem is that you're exporting the runtime from an action file. Actions don't need that. You only need to export the runtime from either a layout or a page file

JJames Heya, can you open an issue on the opennext-cloudflare repo for cron support

M

MarcusAurelius•11/6/24, 10:44 PM

Sure

D

dzoni•11/7/24, 2:19 PM

Hi everyone, my CF builds for next.js just stopped with a message

15:10:34.718    ▲  TypeError: Cannot read properties of undefined (reading 'data')
15:10:34.718    ▲    at N (/opt/buildhome/repo/.next/server/app/_not-found/page.js:120:23074)
15:10:34.719    ▲    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
15:10:34.719    ▲  digest: '879041786'
15:10:34.719    ▲  }

15:10:34.718    ▲  TypeError: Cannot read properties of undefined (reading 'data')
15:10:34.718    ▲    at N (/opt/buildhome/repo/.next/server/app/_not-found/page.js:120:23074)
15:10:34.719    ▲    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
15:10:34.719    ▲  digest: '879041786'
15:10:34.719    ▲  }

15:10:34.718    ▲  TypeError: Cannot read properties of undefined (reading 'data')
15:10:34.718    ▲    at N (/opt/buildhome/repo/.next/server/app/_not-found/page.js:120:23074)
15:10:34.719    ▲    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
15:10:34.719    ▲  digest: '879041786'
15:10:34.719    ▲  }

15:10:34.718    ▲  TypeError: Cannot read properties of undefined (reading 'data')
15:10:34.718    ▲    at N (/opt/buildhome/repo/.next/server/app/_not-found/page.js:120:23074)
15:10:34.719    ▲    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
15:10:34.719    ▲  digest: '879041786'
15:10:34.719    ▲  }

and nothing has changed in the config, I am not using the not found page it is auto-generated. Has anyone experienced similar?

UPDATE: Just fixed by itself after some time, really strange

J

James•11/7/24, 4:42 PM

Sounds like a Next.js issue

P

putty•11/7/24, 10:29 PM

I'm aware that the edge runtime builds as required/requested or something like that but I was wondering request times should by in the 6-8s realm?

J

James•11/8/24, 9:16 AM

Sounds odd. Maybe it's network requests inside the app or very large component trees?

P

putty•11/8/24, 2:26 PM

I do have an API it calls that does roughly take 6s but I have a skeleton UI that should display whilst it's doing so. It functions as intended with the skeleton UI when I'm testing locally.

P

Portram•11/11/24, 3:04 PM

new to next on cloudflare. I just pushed and built my prototype project without adding

export const runtime = "edge"

export const runtime = "edge"

export const runtime = "edge"

export const runtime = "edge" to all of my pages and I exptected to run into issues but so far, everything looks good. What's the expected behaviour? Where should I run into troubles?

P

Portram•11/11/24, 3:09 PM

I also just saw in my logs that all pages have been built as edge function routes uncluding those, where I didn't delcare edge runtime at the top. I'm confused

D

D Trombett•11/11/24, 6:31 PM

You need to add it only to the layout.tsx file

P

putty•11/12/24, 4:26 AM

Normally if there’s issues with the runtime declarations, it’ll show the files/routes in the build log then fail.

DD Trombett You need to add it only to the layout.tsx file

P

Portram•11/12/24, 11:34 AM

thx! I didn't come to a clear conclusion with the current documentation, especially when I reached the point in Trouble Shooting that said one has to make a custom error page with runtime = edge

Pputty Normally if there’s issues with the runtime declarations, it’ll show the files/r...

P

Portram•11/12/24, 11:35 AM

ok so I can expect to run into problems immediately . Thanks!

T

trace•11/12/24, 4:19 PM

Getting this error when I try to deploy a static nextjs application

21:46:54.158     ✓ Generating static pages (5/5)
21:46:54.454       Finalizing page optimization ...
21:46:54.454       Collecting build traces ...
21:46:59.209    
21:46:59.213    Route (app)                              Size     First Load JS
21:46:59.213    ┌ ○ /                                    126 kB          229 kB
21:46:59.213    └ ○ /_not-found                          140 B          87.4 kB
21:46:59.213    + First Load JS shared by all            87.2 kB
21:46:59.213      ├ chunks/23-1198366cbb09edbc.js        31.6 kB
21:46:59.213      ├ chunks/fd9d1056-a7223fb5cd24b6ec.js  53.7 kB
21:46:59.213      └ other shared chunks (total)          1.95 kB
21:46:59.214    
21:46:59.214    
21:46:59.214    ○  (Static)  prerendered as static content
21:46:59.214    
21:46:59.248    Finished
21:46:59.249    Note: No functions dir at /functions found. Skipping.
21:46:59.249    Validating asset output directory
21:46:59.249    Error: Output directory ".vercel/output/static" not found.
21:47:00.202    Failed: build output directory not found

21:46:54.158     ✓ Generating static pages (5/5)
21:46:54.454       Finalizing page optimization ...
21:46:54.454       Collecting build traces ...
21:46:59.209    
21:46:59.213    Route (app)                              Size     First Load JS
21:46:59.213    ┌ ○ /                                    126 kB          229 kB
21:46:59.213    └ ○ /_not-found                          140 B          87.4 kB
21:46:59.213    + First Load JS shared by all            87.2 kB
21:46:59.213      ├ chunks/23-1198366cbb09edbc.js        31.6 kB
21:46:59.213      ├ chunks/fd9d1056-a7223fb5cd24b6ec.js  53.7 kB
21:46:59.213      └ other shared chunks (total)          1.95 kB
21:46:59.214    
21:46:59.214    
21:46:59.214    ○  (Static)  prerendered as static content
21:46:59.214    
21:46:59.248    Finished
21:46:59.249    Note: No functions dir at /functions found. Skipping.
21:46:59.249    Validating asset output directory
21:46:59.249    Error: Output directory ".vercel/output/static" not found.
21:47:00.202    Failed: build output directory not found

21:46:54.158     ✓ Generating static pages (5/5)
21:46:54.454       Finalizing page optimization ...
21:46:54.454       Collecting build traces ...
21:46:59.209    
21:46:59.213    Route (app)                              Size     First Load JS
21:46:59.213    ┌ ○ /                                    126 kB          229 kB
21:46:59.213    └ ○ /_not-found                          140 B          87.4 kB
21:46:59.213    + First Load JS shared by all            87.2 kB
21:46:59.213      ├ chunks/23-1198366cbb09edbc.js        31.6 kB
21:46:59.213      ├ chunks/fd9d1056-a7223fb5cd24b6ec.js  53.7 kB
21:46:59.213      └ other shared chunks (total)          1.95 kB
21:46:59.214    
21:46:59.214    
21:46:59.214    ○  (Static)  prerendered as static content
21:46:59.214    
21:46:59.248    Finished
21:46:59.249    Note: No functions dir at /functions found. Skipping.
21:46:59.249    Validating asset output directory
21:46:59.249    Error: Output directory ".vercel/output/static" not found.
21:47:00.202    Failed: build output directory not found

21:46:54.158     ✓ Generating static pages (5/5)
21:46:54.454       Finalizing page optimization ...
21:46:54.454       Collecting build traces ...
21:46:59.209    
21:46:59.213    Route (app)                              Size     First Load JS
21:46:59.213    ┌ ○ /                                    126 kB          229 kB
21:46:59.213    └ ○ /_not-found                          140 B          87.4 kB
21:46:59.213    + First Load JS shared by all            87.2 kB
21:46:59.213      ├ chunks/23-1198366cbb09edbc.js        31.6 kB
21:46:59.213      ├ chunks/fd9d1056-a7223fb5cd24b6ec.js  53.7 kB
21:46:59.213      └ other shared chunks (total)          1.95 kB
21:46:59.214    
21:46:59.214    
21:46:59.214    ○  (Static)  prerendered as static content
21:46:59.214    
21:46:59.248    Finished
21:46:59.249    Note: No functions dir at /functions found. Skipping.
21:46:59.249    Validating asset output directory
21:46:59.249    Error: Output directory ".vercel/output/static" not found.
21:47:00.202    Failed: build output directory not found

I have output: "export", on next.config.mjs file

Ttrace Getting this error when I try to deploy a static nextjs application ``` 21:46:5...

J

James•11/14/24, 5:36 PM

It looks like you're not using next-on-pages so have the wrong output directory or wrong build command set

P

playsonmac•11/17/24, 2:51 PM

Is there a way to access bindings in a client component? I have a hono worker, and I want to use hono's client rpc features inside a client component

Pplaysonmac Is there a way to access bindings in a client component? I have a hono worker, a...

H

Hello, I’m Allie!•11/17/24, 3:11 PM

If you mean a client-side component, then no

K

Kimitri•11/18/24, 5:49 AM

I'm developing a Nextjs application that I basically will needs the seo features because all my backend is hosted on a external api, so sould I host this project on cloudflare pages or workers?

K

Kimitri•11/18/24, 5:50 AM

this is a personal project so I would like to stay in free tier, so what shoud I chose ?

M

MissS•11/19/24, 4:17 AM

I'm using nextjs with workers on static assets and I'm noticing that even an emptyish project is causing worker CPU usage to spike to several hundred MS

From my standpoint, every page that I'm deploying has "use client" and I'm not doing any API calls. Frankly, everything should be static and so Idk what is even calling workers.

Is there a way to know what endpoint causes the CPU spikes? Or even know what endpoint is considered "static" and what endpoint is actually a worker running

N

num•11/19/24, 9:31 AM

if you do

next build

next build

and it'll show which routes are considered static

○  (Static)   prerendered as static content
●  (SSG)      prerendered as static HTML (uses getStaticProps)
ƒ  (Dynamic)  server-rendered on demand

○  (Static)   prerendered as static content
●  (SSG)      prerendered as static HTML (uses getStaticProps)
ƒ  (Dynamic)  server-rendered on demand

○  (Static)   prerendered as static content
●  (SSG)      prerendered as static HTML (uses getStaticProps)
ƒ  (Dynamic)  server-rendered on demand

○  (Static)   prerendered as static content
●  (SSG)      prerendered as static HTML (uses getStaticProps)
ƒ  (Dynamic)  server-rendered on demand

Nnum if you do `next build` and it'll show which routes are considered static ``` ○ ...

M

MissS•11/19/24, 11:46 AM

Thanks for the reply. So all my pages are static and the only dynamic API call is never made. The API call is hello world anyways

Any ideas what could be hitting my workers and causing the CPU? IDK why worker requests are even being made in the first place. Tails shows requests as I navigate between the static pages i.e. "/dashboard" and it's not clear why

Can't check out, it links to another Discord (`# unknown`). Can you link the PR on GitHub for contex

Similar Threads

Similar Threads

Similar Threads