JThat's because your requests go through the routing system
MI 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.
MI 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
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
How Workers assets' routing and its configuration works.
MThis 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)
JThose 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/
https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/
MOkay, so i should ask the question inside of the workers discussion instead. Thanks
JThere'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
AHey, 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
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"Cloudflare 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.
�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 /error.json3.94KB
�I think the key here is
but doing a Google search didn't get me a lot of good results
but doing a Google search didn't get me a lot of good results
Vhttps://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.
Right out of the oven, consider it bleeding edge and we will stabilize next.
GitHub
@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 &...
/cc @conico974 - I will never thank you enough for all the support!
disclaimers:
it's a preview on an &...
JThe 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?
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?
JISR doesn't work with next-on-pages due to Next.js limitations. The cache API is used for the fetch cache by default
VWe 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
See https://github.com/cloudflare/workers-sdk/discussions/7030#discussioncomment-11393115
TL;DR We bumped the limit to 3MiB for free accounts
Jand 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
JMost 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.
IGood to know - perhaps it should be added to the Workers Changelog (that way it also goes into No Access automatically)?
CGuys... 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!
NAs Chinoman mentioned, since the release of
Every time we try to access we get this error on functions
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)
We'll be appreciated any assistance here, thanks.
@cloudflare/next-on-pages@1.13.6Every time we try to access we get this error on functions
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)
We'll be appreciated any assistance here, thanks.
J
JAs 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_hooksnode:Thanks. It worked wonderful. 
CHey 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
This might be not the correct forum to ask, please let me know if there is another forum related to OpenNext
Jgetting this error
JI'm seeing
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
EDIT 2: seems also related to
✘ TypeError: Illegal invocation: function called with incorrect reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details.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=nextnpx @next/codemod@canary upgrade latestEDIT 2: seems also related to
vercel@39.1.2vercel@39.1.1
BHi, i recommend switching to remix
JI 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
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)
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-pagesI 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)
Ndoes postgres.js work on next on pages already
Nand hyperdrive
NGitHub
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...
Ni see
Nno progress
Nwell- 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
Nturns out it is possible to deploy! Just needs tons of patches. https://github.com/andyjy/mre-pg-nextjs-edge
GitHub
Contribute to andyjy/mre-pg-nextjs-edge development by creating an account on GitHub.
Nmanaged 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
NHey 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
i can run it locally but it does not work after i deploy it
i am deploying a next js serverless app
N@Ahmad Awais Can you please help me solve this issue
CSorry. I have nothing to do with this.
W?pings
SPlease 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.
WIThe 10MiB limit is a hard (architectural) limit currently and can't be increased.
IYou'll have to reduce your bundle size somehow, or split into multiple projects.
THi 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
JI 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
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
vercelnote 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
J--
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
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
MHello,
I am using the next-on-pages package from Cloudflare to release my application under CF Pages. Currently, I am encountering the error: "Exceeds maximum edge function size: 4.18 MB / 4 MB" during deployments. I understand that this issue is caused by the EDGE_FUNCTION_SIZE_LIMIT variable in the @vercel-cli package. Is there a solution on the CF side to increase the value of this variable?
Note: I am using bun.lock, and the patcher does not recognize bun.lock.
I am using the next-on-pages package from Cloudflare to release my application under CF Pages. Currently, I am encountering the error: "Exceeds maximum edge function size: 4.18 MB / 4 MB" during deployments. I understand that this issue is caused by the EDGE_FUNCTION_SIZE_LIMIT variable in the @vercel-cli package. Is there a solution on the CF side to increase the value of this variable?
Note: I am using bun.lock, and the patcher does not recognize bun.lock.
