ISR doesn't work with next-on-pages due to Next.js limitations. The cache API is used for the fetch
ISR 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.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
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_hooks without a node: prefix, so it requires the newer version of nodejs_compat which was updated on compat dates after Sept 23rd.NThanks. 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 this reference. See https://developers.cloudflare.com/workers/observability/errors/#illegal-invocation-errors for details. on 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 and then running npx @next/codemod@canary upgrade latest shows the same error, filed https://github.com/cloudflare/next-on-pages/issues/912EDIT 2: seems also related to
vercel@39.1.2, forcing vercel@39.1.1 fixes it.
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 in dev
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
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 greatnote 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 CLI should fix it)
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.
Sanyone getting on og image generation?
SI had it working before updating my compat date
Spinning vercel to 39.1.1 fixed it
MHi guys, this might be a long shot, but has anyone successfully established a WebSocket connection to a Durable Object through a Nextjs pages application? I am unable to catch the WebSocket connection request in Nextjs. This is required because all the authentication logic, which relies on D1, resides in the pages app.
JJust a note that Next.js 15 is not officially supported at this time, and Vercel keeps making it more painful as evidenced by breaking changed in the vercel cli for us
R
JHi all. I'm curious, is something in the works to make previewing with workerd (
npm run pages:build && wrangler pages dev) similar to running the Next.js dev server in terms of speed? Right now it feels quite cumbersome in comparison to Next with turbopack or Vite because of 15+ second build times. Or is the OpenNext initiative looking to resolve this? By making then runtimes similar when using the Next.js dev server vs deployed on Pages?
CHi, I use next-on-pages, and when I deploy, the libraries that use
Do you have any idea for a fix?
process.env.CUSTOM_VAR cannot find my envDo you have any idea for a fix?
RI use remix so don't know for sure, but this might help: https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/bindings/ ?
Jnext-on-pages has a way for you to use the next dev server for local dev - https://github.com/cloudflare/next-on-pages/tree/main/internal-packages/next-dev
As for OpenNext, it would be better to put that question in the OpenNext discord, but it's certainly possible for something similar to be done for that adapter if needed
As for OpenNext, it would be better to put that question in the OpenNext discord, but it's certainly possible for something similar to be done for that adapter if needed
JI am using the Next dev server locally a lot and
setupDevPlatform is definitely helpful there. But sometimes I have to debug an issue due to the subtle differences between runtimes of next devwrangler pages devnpx @cloudflare/next-on-pages --watch, and then re-run wrangler pages dev--live-reload functionality of wrangler pages dev
0Any update on nextJS cloudfalre deploy - my build was working well before, but tonight rebuild hit an issue
Nothing wrong with local build
Nothing wrong with local build
0GitHub
next-on-pages environment related information No response Description it buid is good yesterday, but it is error today, i do nothing of my code this is the error 14:15:26.583 ▲ ./src/app/[lang]/lay...
