Set an environment variable (in the Pages settings) of `NODE_VERSION` and a value of `20`
Set an environment variable (in the Pages settings) of
NODE_VERSION and a value of 20
MWe just have a lot of routes yeah.
I have everything as edge runtime right now preventing some of the routes that could be statically rendered to be static.
But as far as i understood it, thats kinda the limitation here. Does this just mean next on pages has a "soft route limit"?
I have everything as edge runtime right now preventing some of the routes that could be statically rendered to be static.
But as far as i understood it, thats kinda the limitation here. Does this just mean next on pages has a "soft route limit"?
Ystill failed
IWhat does the error say in the logs?
Ywell make me try create ".env" file to fix that?
I.env file won't work, that's not a thing that changes the Node version
YYBuild system version are V2, and I try Variables and Secrets: Plaintext, NODE_VERSION, 20YIs any I did wrong? 
IMake sure you don't have a space in your environment variable?
IJust
20yup sir not have space
IDo you have a
.node-version or .nvmrc file in your project?Ynope it new from the Pages Nextjs SSR docs like I said just follow the command
Yokay I fix it but it just need manual add like 
.nvmrc and input 20might add this tip in docs?
Yfollow at this cf thread https://community.cloudflare.com/t/node-version-is-being-ignored/657974/2
Dcan anybody help
JMost likely not, that API is not implemented in workerd - https://github.com/cloudflare/workerd/issues/3273
GitHub
The MessageChannel API is available on node but not CF Workers. This is causing an issue during the deployment of sites using React 19 + Astro + Workers, see facebook/react#31827 and withastro/astr...
DIs there any other way to send emails from cloudflare environment?
JI do not know
ADoes cloudflare pages support react server actions ?
A
Ccloudflare pages nextjs, caching on KV not populating. Followed the steps as given in below documentation, but nothing gets populated on KV store.
https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/caching/#workers-kv-recommended
https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/caching/#workers-kv-recommended
Cloudflare Docs
@cloudflare/next-on-pages supports caching and revalidating data returned by subrequests you make in your app by calling fetch().
JThat runtime export is a page/layout level concern, so I think it's just being put in the wrong place
YI have a nextjs project which is using next on pages to build it for the cloudflare pages platform. I followed the documentation here: https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/get-started/
I am also using D1 as my database. Running the development server, I can send requests to my
The problem comes when I run a build preview using this
It builds the project perfectly fine and I am using the
When the wrangler dev server starts and I make a request to my
I don't know why I am getting this error and how do i fix it? Please help.
I am using this version of
I am also using D1 as my database. Running the development server, I can send requests to my
/api/waitlist route, where waitlist is the route defined, and I am able to save data to my local D1 correctly.The problem comes when I run a build preview using this
package.json script: "preview": "npm run cfbuild && wrangler pages dev --port 3005". It builds the project perfectly fine and I am using the
experimental-edge runtime.When the wrangler dev server starts and I make a request to my
/api/waitlist route, it is throwing the following error:I don't know why I am getting this error and how do i fix it? Please help.
I am using this version of
"@cloudflare/next-on-pages": "^1.13.7", in my package.json.JCan you make sure your compatibility date is after Sept 23rd
YJust checked, it isn't. What should I change it to?
I can't find any mention of distinct comptability date options
I can't find any mention of distinct comptability date options
Yin documentation
YI changed it to 2024-09-24 and it worked.
Thank you so much. I have been stuck on this all day.
It would be better if these things are present in the documentation.
Thank you so much. I have been stuck on this all day.
It would be better if these things are present in the documentation.
Jit's becaues next.js/vercel made a change that only works with the new version of nodejs_compat_v2 and that was merged into nodejs_compat on sept 23rd - https://developers.cloudflare.com/workers/runtime-apis/nodejs/#get-started
V------------------------------
This channel is archived. The product is still supported and can receive community support in pages-help
------------------------------
This channel is archived. The product is still supported and can receive community support in pages-help
------------------------------
