hey y'all... I've recently moved to using cloudflare pages with nextjs 14 instead of vercel. I have

hey y'all... I've recently moved to using cloudflare pages with nextjs 14 instead of vercel. I have a functions folder which isn't being picked up automatically for deployment - is this because each of those folders have their own wrangler.toml?

zemonstasOP•10/23/24, 4:35 AM

this isn't a complaint BTW, I prefer this feature. just wandering if that's something I can depend on in future...?

Jakov•10/23/24, 10:11 AM

Can anyone help me with pages-help ? If I don't do it soon I might lose my job

Zzemonstas hey y'all... I've recently moved to using cloudflare pages with nextjs 14 instea...

tadhglewis•10/23/24, 12:59 PM

You shouldn't use

functions

functions

folder. Instead you should use standard NextJS API handlers: https://nextjs.org/docs/app/building-your-application/routing/route-handlers

Routing: Route Handlers | Next.js

Create custom request handlers for a given route using the Web's Request and Response APIs.

Ccardyet Anyone have a guide of how to use the functions folder with nextjs on pages, I c...

Hello, I’m Allie!•10/23/24, 2:28 PM

next-on-pages(or any SSR framework) will generate functions for you, which overrides anything you put in the folder yourself. You need to use Next's API Routes instead of the functions folder

Routing: API Routes | Next.js

Next.js supports API Routes, which allow you to build your API without leaving your Next.js app. Learn how it works here.

Ccardyet ahh, but that then will use the next edge runtime I think so we have this node m...

Hello, I’m Allie!•10/23/24, 6:14 PM

Oh, you meant static Next? Then the functions folder should work fine

mokka 🍘•10/23/24, 7:19 PM

Hi i'm struggling to understand how i can fix this error, does anyone know how i can resolve it? sorry im new

James•10/23/24, 7:42 PM

That is an error from the Next.js build, so I would recommend making an issue on Next.js repo.

Jakov•10/23/24, 7:46 PM

Next.JS 15 requires nodejs version 18.18.0, but Cloudflare's is 18.17.1
When I change NODE_VERSION env variable, it just does not change it. Anyone knows how to fix this?

Ccardyet nope, not static, but I want to use workers alongside. The problem, I'm pretty s...

Hello, I’m Allie!•10/23/24, 7:48 PM

Wait, so do you mean you want to host your project on a different service?

Ccardyet sorry, totally not explaining myself well. I want to deploy a Full-stack applica...

Hello, I’m Allie!•10/23/24, 10:06 PM

The Edge Runtime is a Worker, if that is what you mean

Hello, I’m Allie!•10/23/24, 10:06 PM

No part of the Cloudflare platform can run full Node in a user-facing way if that is what you mean

Ttadhglewis You shouldn't use `functions` folder. Instead you should use standard NextJS API...

zemonstasOP•10/24/24, 12:10 AM

Not quite my question. I have real workers indirectly associated with the nextjs api handlers written previously. These functions are not being automatically picked up when the build process runs. I'm hoping that this behaviour continues. I don't want to re-write them as NextJS API routes... yet.

Ccardyet sorry, totally not explaining myself well. I want to deploy a Full-stack applica...

tadhglewis•10/24/24, 12:17 AM

You should try OpenNext CloudFlare adapter. It allows you to use node runtime but it still has limitations and it's actively being developed

Zzemonstas Not quite my question. I have real workers indirectly associated with the nextjs...

Isaac McFadyen•10/24/24, 1:16 AM

Bit confused what you mean. When deploying a Next.js site with Pages, it won't deploy a Worker alongside it... you can either use Next.js API routes or a worker that's deployed seperately (not in CI). Pages won't deploy the Workers for you.

Isaac McFadyen•10/24/24, 1:17 AM

If you mean a function as in Pages Functions then Lewis is correct, the /functions folder is completely ignored when using next-on-pages and you'll have to either move to a Next.js API route or use a seperately deployed Worker.

zemonstasOP•10/24/24, 2:56 AM

OK great - that clears up my confusion but not yours

This is by far the best outcome - what wasn't clear is if /functions is ignored or not with next-on-pages. If it is, that's ideal for me though I would love it if I could bundle up CI deployments with specific workers in the /functions folder in the future. More of an 'opt-in'. The reason for this was previously I was using Vercel and hated their edge functions, preferring the Cloudflare workers for mostly everything that wasn't specific to the exact domain I was building in. Now that I'm on Cloudflare for everything I can make this delineation a bit more strict based on application affinity than infrastructure affinity.

JJakov Can anyone help me with <#1063191651796914276> ? If I don't do it soon I might l...

R in Tokyo•10/24/24, 5:09 AM

Did you get help yet?

Ted•10/24/24, 11:12 AM

Moving question as I have deployed next on workers...

Jon•10/24/24, 8:20 PM

Is there a way to use npm install --forcenpm install --force when deploying next to cloudflare pages?

Jon•10/24/24, 8:21 PM

On vercel, I'm able to override just the install command:

Jon•10/24/24, 8:22 PM

That option is not present on cloudflare

Khagan•10/24/24, 8:24 PM

23:16:38.104    Cloning repository...
23:16:39.261    From https://github.com/kaankutan/kutan.dev
23:16:39.261     * branch            93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261    
23:16:39.305    HEAD is now at 93d203e Image optimization added
23:16:39.306    
23:16:39.390    
23:16:39.391    Using v2 root directory strategy
23:16:39.417    Success: Finished cloning repository files
23:17:32.083    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083    Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

23:16:38.104    Cloning repository...
23:16:39.261    From https://github.com/kaankutan/kutan.dev
23:16:39.261     * branch            93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD
23:16:39.261    
23:16:39.305    HEAD is now at 93d203e Image optimization added
23:16:39.306    
23:16:39.390    
23:16:39.391    Using v2 root directory strategy
23:16:39.417    Success: Finished cloning repository files
23:17:32.083    Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH
23:17:32.083    Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

Khagan•10/24/24, 8:25 PM

I'm getting this error. Any solution?

KKhagan ``` 23:16:38.104 Cloning repository... 23:16:39.261 From https://github.co...

Walshy•10/24/24, 8:29 PM

consistently getting it?

WWalshy consistently getting it?

Khagan•10/24/24, 8:29 PM

Walshy•10/24/24, 8:29 PM

let me escalate it up

Khagan•10/24/24, 9:06 PM

To test it, I pushed a different commit without changing anything. It is running now. Intersting. @Walshy

Donda•10/24/24, 9:16 PM

Hey everyone does anyone know where can I read about multi tenant project with cloud flare and nextjs

DoggeSlapper•10/25/24, 8:28 AM

anyone tried nextjs 15 on pages?

DDoggeSlapper anyone tried nextjs 15 on pages?

fry69•10/25/24, 8:30 AM

Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/supported-features/

Ffry69 Not yet supported, only 13 and 14 are so far -> https://developers.cloudflare.co...

DoggeSlapper•10/25/24, 8:31 AM

yeah I saw is not supported, but didnt expect it either to be officially listed considering it's so new

DDoggeSlapper yeah I saw is not supported, but didnt expect it either to be officially listed ...

fry69•10/25/24, 8:31 AM

Well, then try out and find out?

Ffry69 Well, then try out and find out?

DoggeSlapper•10/25/24, 8:32 AM

ye I will probably do, just trying 14 for now. Then will see

DDoggeSlapper ye I will probably do, just trying 14 for now. Then will see

fry69•10/25/24, 8:33 AM

There are some neat things is 15, but I think I'll wait until React 19 is out

Ffry69 There are some neat things is 15, but I think I'll wait until React 19 is out

DoggeSlapper•10/25/24, 8:34 AM

I was using canary already for some other project I have on remix and was thinking giving it a shot

DoggeSlapper•10/25/24, 8:35 AM

is normal that my deploy appear on the pages.dev subdomain but not on the linked domain yet (linked domain appear as active already on the pages dashboard of cloudflare)

DDoggeSlapper is normal that my deploy appear on the pages.dev subdomain but not on the linked...

fry69•10/25/24, 8:40 AM

Not tried pages yet, but for simple static asset only worker I know this works to deploy a static website ->

name = "some-name"
compatibility_date = "2024-10-18"
assets = { directory = "./public" }
routes = [
  { pattern = "test.example.com", custom_domain = true }
]

name = "some-name"
compatibility_date = "2024-10-18"
assets = { directory = "./public" }
routes = [
  { pattern = "test.example.com", custom_domain = true }
]

Ffry69 There are some neat things is 15, but I think I'll wait until React 19 is out

DoggeSlapper•10/25/24, 8:41 AM

yeah specially canary, "use cache" looks dope

Ffry69 Not tried pages yet, but for simple static asset only worker I know this works t...

DoggeSlapper•10/25/24, 8:46 AM

Something is off with my deploy It only works when I have the log streaming enabled o.O

DoggeSlapper•10/25/24, 8:46 AM

JJames You are welcome to make a docs PR if you would like to 🙂

hsnilsson•10/25/24, 8:47 AM

Might be hard for me to phrase it for you (it means that note would include a statement about where those products are heading in terms of support - which is usually something that triggers internal discussions around the phrasings

). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788
"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does

GitHub

Update get-started.mdx by hsnilsson · Pull Request #17788 · cloudfl...

Summary
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...

Vveeque Come think of it, the comment you mentioned could be all that needs to be added ...

hsnilsson•10/25/24, 8:49 AM

https://github.com/cloudflare/cloudflare-docs/pull/17788 You can help phrase it better (or completely different) by commenting on the PR I did now.

DDoggeSlapper Click to see attachment

DoggeSlapper•10/25/24, 9:07 AM

@fry69 lol I forgot I used next15 xD

DoggeSlapper•10/25/24, 9:07 AM

guess that's the issue

DDoggeSlapper anyone tried nextjs 15 on pages?

num•10/25/24, 12:03 PM

I did but i'm having errors due to some static routes not being able to be build with next on pages

23:16:38.104 Cloning repository... 23:16:39.261 From https://github.com/kaankutan/kutan.dev 23:16:39.261 * branch 93d203ed7a7c38795b849e34333e737c69d76c0d -> FETCH_HEAD 23:16:39.261 23:16:39.305 HEAD is now at 93d203e Image optimization added 23:16:39.306 23:16:39.390 23:16:39.391 Using v2 root directory strategy 23:16:39.417 Success: Finished cloning repository files 23:17:32.083 Failed: an internal error occurred. If this continues, contact support: https://cfl.re/3WgEyrH 23:17:32.083 Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 755daaa4-ad45-428f-be89-84e3a2857977

hey y'all... I've recently moved to using cloudflare pages with nextjs 14 instead of vercel. I have

Similar Threads

Similar Threads

Similar Threads