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

JamesOP•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

JamesOP•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

JamesOP•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

JamesOP•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

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

MMissS Thanks for the reply. So all my pages are static and the only dynamic API call i...

H

Hello, I’m Allie!•11/19/24, 2:50 PM

If everything is static, why not just get rid of next-on-pages? then you can’t be billed at all

MMissS Thanks for the reply. So all my pages are static and the only dynamic API call i...

J

JamesOP•11/19/24, 2:51 PM

That's because your requests go through the routing system

HHello, I’m Allie!If everything is static, why not just get rid of <#1135899572141568050>? then yo...

M

MissS•11/19/24, 2:54 PM

I could do this, but I want to eventually use the nextjs api routes, and so doing that would require me to have two seperate deployments.

JJames That's because your requests go through the routing system

M

MissS•11/19/24, 3:02 PM

I swear I've read https://developers.cloudflare.com/workers/static-assets/routing/ several times and also thrown it into perplexity to see if it'll help explain my situation but I feel like the actual experience is different from the documentation.

From the documentation, it seems like requests to static pages (i.e. "dashboard" should not be hitting a worker but tails and baselime show that it does). In addition i'm suspecting that for whatever reason that this sometimes causes several hundred ms of CPU usage

Cloudflare Docs

Routing | Cloudflare Workers docs

How Workers assets' routing and its configuration works.

MMissS I swear I've read https://developers.cloudflare.com/workers/static-assets/routin...

M

MissS•11/19/24, 3:05 PM

This is a screenshot from the documentation, and from my exerience, visiting "blog" would actually hit a worker. Since this example is seemingly identical to me visiting "dashboard" that is shown to be static on deployment (I'm using nextjs on workers)

J

JamesOP•11/19/24, 3:38 PM

Those are the Workers docs not the Pages docs - next-on-pages is for Pages. The Cloudflare Pages docs has a section for deploying Next.js which touches on this a bit.
https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/

JJames Those are the Workers docs not the Pages docs - next-on-pages is for Pages. The ...

M

MissS•11/19/24, 9:56 PM

Okay, so i should ask the question inside of the workers discussion instead. Thanks

J

JamesOP•11/20/24, 8:29 AM

There's a lot of work going on to re-use parts of the AWS adapter and share the same architecture between the two. This is mostly happening in the experimental branch but also requires a lot of changes in the AWS adaptor to make re-use easier. So there's still things happening, and you can try them out with

https://pkg.pr.new/@opennextjs/cloudflare@experimental

https://pkg.pr.new/@opennextjs/cloudflare@experimental

https://pkg.pr.new/@opennextjs/cloudflare@experimental

https://pkg.pr.new/@opennextjs/cloudflare@experimental. I would recommend using the OpenNext discord for discussions about that adaptor.

A

amr•11/20/24, 8:24 PM

Hey, is it possible to export a Workflow or a Queue handler in a Pages' custom worker entrypoint that's mentioned here? https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/advanced/
or are only fetch handlers supported i.e. I would either have to create a new worker or migrate to the experimental opennext?

edit: it's not supported got

Configuration file for Pages projects does not support "workflows"

Configuration file for Pages projects does not support "workflows"

Configuration file for Pages projects does not support "workflows"

Configuration file for Pages projects does not support "workflows"

Cloudflare Docs

Advanced Usage | Cloudflare Pages docs

If you need to run code before or after your Next.js application, create your own Worker entrypoint and forward requests to your Next.js application.

�

🕊Freedom🕊•11/21/24, 11:41 PM

I was getting the following issue with my website, using edge runtime SSR and nextjs-auth0. It would load for users but it'd emit an error 500 when

GET /

GET /

GET /

GET /, resulting in bad SEO, since Google thinks it's down. Had to switch to Vercel. Anyone know how to fix this error?

error.json3.94KB

�

🕊Freedom🕊•11/21/24, 11:48 PM

I think the key here is

[
    {
      "message": [
        "TypeError: Illegal invocation: function called with incorrect `this` reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details."
      ],
      "level": "error",
      "timestamp": 1732129720148
    },
    {
      "message": [
        "error code: 1016"
      ],
      "level": "error",
      "timestamp": 1732129720300
    },
    {
      "message": [
        "Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
      ],
      "level": "error",
      "timestamp": 1732129720300
    }
  ]

[
    {
      "message": [
        "TypeError: Illegal invocation: function called with incorrect `this` reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details."
      ],
      "level": "error",
      "timestamp": 1732129720148
    },
    {
      "message": [
        "error code: 1016"
      ],
      "level": "error",
      "timestamp": 1732129720300
    },
    {
      "message": [
        "Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
      ],
      "level": "error",
      "timestamp": 1732129720300
    }
  ]

[
    {
      "message": [
        "TypeError: Illegal invocation: function called with incorrect `this` reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details."
      ],
      "level": "error",
      "timestamp": 1732129720148
    },
    {
      "message": [
        "error code: 1016"
      ],
      "level": "error",
      "timestamp": 1732129720300
    },
    {
      "message": [
        "Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
      ],
      "level": "error",
      "timestamp": 1732129720300
    }
  ]

[
    {
      "message": [
        "TypeError: Illegal invocation: function called with incorrect `this` reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details."
      ],
      "level": "error",
      "timestamp": 1732129720148
    },
    {
      "message": [
        "error code: 1016"
      ],
      "level": "error",
      "timestamp": 1732129720300
    },
    {
      "message": [
        "Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
      ],
      "level": "error",
      "timestamp": 1732129720300
    }
  ]

but doing a Google search didn't get me a lot of good results

Ccardyet How's opennext going? There hasn't been a release in 1 month, I thought there w...

V

Victor Berchet•11/22/24, 2:28 PM

https://github.com/opennextjs/opennextjs-cloudflare/pull/140 is what we were up to lately...
Right out of the oven, consider it bleeding edge and we will stabilize next.

GitHub

feat: integrate the OpenNext server by vicb · Pull Request #140 · o...

@dario-piotrowicz @james-elicx @petebacondarwin Here is what I have been working on.
/cc @conico974 - I will never thank you enough for all the support!
disclaimers:

it's a preview on an &...

J

Javert•11/26/24, 10:36 AM

The Cache API for cloudflare pages says it automatically works with Next.js https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/caching/

My question is what does the "deafult" mean, what is it used for by default, because from what I see by default it does not cache anything, we would need to integrate that cache inside our app logic to make it work?

I am also guessing it does not automatically cache ISR pages since ISR does not really work with edge runtime. https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/caching/

Anyone has some concrete experience with this?

J

JamesOP•11/27/24, 8:45 AM

ISR doesn't work with next-on-pages due to Next.js limitations. The cache API is used for the fetch cache by default

V

Victor Berchet•11/27/24, 10:31 AM

We have an update for people hitting the 1MiB size limit on free accounts
See https://github.com/cloudflare/workers-sdk/discussions/7030#discussioncomment-11393115
TL;DR We bumped the limit to 3MiB for free accounts

JJames ISR doesn't work with next-on-pages due to Next.js limitations. The cache API is...

J

Javert•11/27/24, 3:16 PM

and fetch cache is not used for Next.js pages directory so what I found is that on pages directory your only option is getServerSideProps and cache through cloudflare domain proxy

J

Javert•11/27/24, 3:17 PM

Most of the docs for Next.js https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/ actually applies to app router more then pages directory, which was not clear to me from the get go.

VVictor Berchet We have an update for people hitting the 1MiB size limit on free accounts See ht...

I

Isaac McFadyen•11/27/24, 5:27 PM

Good to know - perhaps it should be added to the Workers Changelog (that way it also goes into No Access automatically)?

C

Chinoman10•11/28/24, 4:54 PM

Guys... the last patch/build you released ~3h ago for next-on-pages broke our project... we're getting 500 errors even if we rollback our deployments!

N

nuno•11/28/24, 5:03 PM

As Chinoman mentioned, since the release of

@cloudflare/next-on-pages@1.13.6

@cloudflare/next-on-pages@1.13.6

@cloudflare/next-on-pages@1.13.6

@cloudflare/next-on-pages@1.13.6 we can't access our website, the deployment is successful, but access the website itself it's impossible and always return the 500 error page.

Every time we try to access we get this error on functions

"Error: No such module \"__next-on-pages-dist__/functions/src/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/src/middleware.func.js\""

"Error: No such module \"__next-on-pages-dist__/functions/src/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/src/middleware.func.js\""

"Error: No such module \"__next-on-pages-dist__/functions/src/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/src/middleware.func.js\""

"Error: No such module \"__next-on-pages-dist__/functions/src/async_hooks\".\n  imported from \"__next-on-pages-dist__/functions/src/middleware.func.js\""

We already tried to use other versions to build the project, but with no success, we get this error instead (using 1.13.5 and 1.13.2)

✘ [ERROR] Could not resolve "async_hooks"
16:58:59.136    
16:58:59.136        <stdin>:379:680:
16:58:59.136          379 │ ...:()=>N});var R=A(require("async_hooks")),S="@next/request-cont...
16:58:59.136              ╵                             ~~~~~~~~~~~~~
16:58:59.137    
16:58:59.137      The package "async_hooks" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "async_hooks"
16:58:59.136    
16:58:59.136        <stdin>:379:680:
16:58:59.136          379 │ ...:()=>N});var R=A(require("async_hooks")),S="@next/request-cont...
16:58:59.136              ╵                             ~~~~~~~~~~~~~
16:58:59.137    
16:58:59.137      The package "async_hooks" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "async_hooks"
16:58:59.136    
16:58:59.136        <stdin>:379:680:
16:58:59.136          379 │ ...:()=>N});var R=A(require("async_hooks")),S="@next/request-cont...
16:58:59.136              ╵                             ~~~~~~~~~~~~~
16:58:59.137    
16:58:59.137      The package "async_hooks" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

✘ [ERROR] Could not resolve "async_hooks"
16:58:59.136    
16:58:59.136        <stdin>:379:680:
16:58:59.136          379 │ ...:()=>N});var R=A(require("async_hooks")),S="@next/request-cont...
16:58:59.136              ╵                             ~~~~~~~~~~~~~
16:58:59.137    
16:58:59.137      The package "async_hooks" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.

We'll be appreciated any assistance here, thanks.

J

JamesOP•11/28/24, 5:23 PM

J

JamesOP•11/28/24, 5:24 PM

As mentioned on the GitHub issue, please bump your compatibility date so that you are using the newer version of nodejs_compat - Vercel forced every build to have

async_hooks

async_hooks

async_hooks

async_hooks without a

node:

node:

prefix, so it requires the newer version of nodejs_compat which was updated on compat dates after Sept 23rd.

JJames As mentioned on the GitHub issue, please bump your compatibility date so that yo...

N

nuno•11/28/24, 5:35 PM

Thanks. It worked wonderful. chef_kiss

C

can•11/28/24, 7:20 PM

Hey y'all, i'm trying to use OpenNext for my next application and I saw that middlewares are not supported. How should we handle auth logic if middlewares are not supported? https://opennext.js.org/cloudflare#not-yet-supported-nextjs-features

This might be not the correct forum to ask, please let me know if there is another forum related to OpenNext

J

JOEY•11/29/24, 12:28 PM

getting this error

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

Similar Threads

Similar Threads

Similar Threads