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

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

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

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

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

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

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

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

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

J

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

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

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 /

, 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

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

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

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

J

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

J

juanferreras•11/29/24, 12:38 PM

I'm seeing

✘ TypeError: Illegal invocation: function called with incorrect

✘ TypeError: Illegal invocation: function called with incorrect

✘ TypeError: Illegal invocation: function called with incorrect

✘ TypeError: Illegal invocation: function called with incorrect this

 reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details.

reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details.

 reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details.

reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details. on

next@15.0.3
@cloudflare/next-on-pages@1.13.6
wrangler@3.91.0

next@15.0.3
@cloudflare/next-on-pages@1.13.6
wrangler@3.91.0

next@15.0.3
@cloudflare/next-on-pages@1.13.6
wrangler@3.91.0

next@15.0.3
@cloudflare/next-on-pages@1.13.6
wrangler@3.91.0

seems to affect Next.js 15 App Router when using Route Handlers – will see if I can create a simple repro or it depends on any specifics of this small pet project. (I had it running with nodejs_compat_v1 so it might as well be that)

points to this https://github.com/vercel/next.js/blob/canary/packages/next/src/server/web/spec-extension/fetch-event.ts#L37-L49
likely introduced in https://github.com/vercel/next.js/pull/71309 which released in 15.0.0-canary => rc => stable

EDIT: yeah a fresh

npm create cloudflare@latest -- my-next-app --framework=next

npm create cloudflare@latest -- my-next-app --framework=next

npm create cloudflare@latest -- my-next-app --framework=next

npm create cloudflare@latest -- my-next-app --framework=next and then running

npx @next/codemod@canary upgrade latest

npx @next/codemod@canary upgrade latest

npx @next/codemod@canary upgrade latest

npx @next/codemod@canary upgrade latest shows the same error, filed https://github.com/cloudflare/next-on-pages/issues/912

EDIT 2: seems also related to

vercel@39.1.2

vercel@39.1.2

vercel@39.1.2

vercel@39.1.2, forcing

vercel@39.1.1

vercel@39.1.1

vercel@39.1.1

vercel@39.1.1 fixes it.

Jjuanferreras I'm seeing `✘ TypeError: Illegal invocation: function called with incorrect `thi...

B

bun•11/29/24, 5:44 PM

Hi, i recommend switching to remix

Bbun Hi, i recommend switching to remix

J

juanferreras•11/29/24, 5:53 PM

I don't (or at least, not for just compat reasons alone)!

Next.js has a few things that makes it specifically difficult to run outside of Vercel – but the company I work for runs

next-on-pages

next-on-pages

in production with a lot of traffic quite successfully. It's a lot of effort for Cloudflare & co (and the individual contributors like James) to chase the ever-moving goal post, but with a bit of fiddling and pinning dependencies responsively, it runs perfectly.

I think nodejs_compat_v2 + opennext + 3mb free bundle size is on track to make a potentially brighter future for the dev experience specifically (and less issues with the workerd runtime not supporting some dependencies)

N

neoney•11/29/24, 9:16 PM

does postgres.js work on next on pages already

N

neoney•11/29/24, 9:16 PM

and hyperdrive

N

neoney•11/29/24, 9:18 PM

https://github.com/cloudflare/workers-sdk/issues/5555

GitHub

🚀 Feature Request: cloudflare module polyfills for node.js runtime ...

Describe the solution Implement polyfills to allow modules like cloudflare:sockets to be used in dev mode for cloudflare pages projects. Currently, it is only possible to use those projects when ru...

N

neoney•11/29/24, 9:18 PM

i see

N

neoney•11/29/24, 9:18 PM

no progress

N

neoney•11/29/24, 10:58 PM

well- cloudflare:sockets should work in production, but I can't use it in dev. Is there some alternative to it? Like i'd like to be able to just use the raw nodejs modules in dev mode... idk if that's doable though

N

neoney•11/30/24, 5:15 PM

turns out it is possible to deploy! Just needs tons of patches. https://github.com/andyjy/mre-pg-nextjs-edge

GitHub

GitHub - andyjy/mre-pg-nextjs-edge

Contribute to andyjy/mre-pg-nextjs-edge development by creating an account on GitHub.

N

neoney•11/30/24, 6:44 PM

managed to get it working both when deployed and in dev mode, needs patching all those pg packages and nextjs as well to allow using

net

net

net

net in dev

N

Narasimha•12/1/24, 8:42 AM

Hey can some one help me i am getting Illegal Invocation error ,
i can run it locally but it does not work after i deploy it
i am deploying a next js serverless app

N

Narasimha•12/1/24, 8:45 AM

@Ahmad Awais Can you please help me solve this issue

N

Narasimha•12/1/24, 12:15 PM

Hey @cb can I get some help ??

C

cb•12/1/24, 1:24 PM

Sorry. I have nothing to do with this.

W

Walshy•12/1/24, 1:44 PM

?pings

S

SuperHelpflare•12/1/24, 1:44 PM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

W

Walshy•12/1/24, 1:44 PM

Read: https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors

Original message was deleted

I

Isaac McFadyen•12/2/24, 2:44 AM

The 10MiB limit is a hard (architectural) limit currently and can't be increased.

I

Isaac McFadyen•12/2/24, 2:44 AM

You'll have to reduce your bundle size somehow, or split into multiple projects.

T

thipperz•12/3/24, 1:33 AM

Hi there, is the next-on-pages adapter fully compatible with Next 15? I want to know if I can safely update. My project is currently running Next 14.2.16

Tthipperz Hi there, is the next-on-pages adapter fully compatible with Next 15? I want to ...

J

juanferreras•12/3/24, 1:43 PM

I don't know if officially (the CLI from Cloudflare still ships v14 by default) – but as long as you watch for this issue https://github.com/cloudflare/next-on-pages/issues/912 (e.g. temporarily pin down

vercel

vercel

vercel

vercel CLI version), I've got a pet project deployed to Pages with next 15.0.3, app router, apis/middleware, etc and it's working great

note if you upgrade to next-on-pages@1.13.6 (https://github.com/cloudflare/next-on-pages/releases/tag/%40cloudflare%2Fnext-on-pages%401.13.6) - you'll need to run the new Node.js compat v2 (you should just update your compatibility date if it's older than Sept 23), see https://developers.cloudflare.com/workers/runtime-apis/nodejs/#nodejs-api-polyfills

NNarasimha Hey can some one help me i am getting Illegal Invocation error , i can run it lo...

J

juanferreras•12/3/24, 1:47 PM

--
you might be running into this (https://github.com/cloudflare/next-on-pages/issues/912). However, it should also fail locally when you build (e.g. https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#build-and-preview-your-application-locally), so it could be a different issue. If it's the same, temporarily pinning down the

vercel

vercel

vercel

vercel CLI should fix it)

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

Similar Threads

Similar Threads

Similar Threads