Not quite my question. I have real workers indirectly associated with the nextjs api handlers writte

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

T

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

I

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.

I

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.

Z

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

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

Did you get help yet?

T

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

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

J

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

Is there a way to use

npm install --force

npm install --force

when deploying next to cloudflare pages?

J

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

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

J

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

That option is not present on cloudflare

K

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

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

K

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

W

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

consistently getting it?

WWalshy consistently getting it?

K

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

W

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

let me escalate it up

K

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

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

D

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

D

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

anyone tried nextjs 15 on pages?

DDoggeSlapper anyone tried nextjs 15 on pages?

F

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

D

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

F

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

Well, then try out and find out?

Ffry69 Well, then try out and find out?

D

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

F

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

D

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

D

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

F

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 }
]

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

D

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

D

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

D

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

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

H

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

H

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

D

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

@fry69 lol I forgot I used next15 xD

D

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

guess that's the issue

DDoggeSlapper anyone tried nextjs 15 on pages?

N

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

RR in Tokyo Did you get help yet?

J

Jakov•10/26/24, 12:27 PM

NO sad

F

fluf•10/26/24, 4:40 PM

Cloudflare asked me to export const runtime = "edge" in order to run my api routes, and after adding them it still won't build and gives the same errors:

01:52:20.142    ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142    ⚡️ 
01:52:20.142    ⚡️     The following routes were not configured to run with the Edge Runtime:
01:52:20.143    ⚡️       - /_not-found
01:52:20.143    ⚡️       - /index
01:52:20.143    ⚡️       - /login
01:52:20.143    ⚡️       - /settings
01:52:20.143    ⚡️       - /users
01:52:20.143    ⚡️       - /websites/[id]
01:52:20.143    ⚡️       - /websites
01:52:20.144    ⚡️ 
01:52:20.144    ⚡️     Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144    ⚡️       export const runtime = 'edge';

01:52:20.142    ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142    ⚡️ 
01:52:20.142    ⚡️     The following routes were not configured to run with the Edge Runtime:
01:52:20.143    ⚡️       - /_not-found
01:52:20.143    ⚡️       - /index
01:52:20.143    ⚡️       - /login
01:52:20.143    ⚡️       - /settings
01:52:20.143    ⚡️       - /users
01:52:20.143    ⚡️       - /websites/[id]
01:52:20.143    ⚡️       - /websites
01:52:20.144    ⚡️ 
01:52:20.144    ⚡️     Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144    ⚡️       export const runtime = 'edge';

01:52:20.142    ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142    ⚡️ 
01:52:20.142    ⚡️     The following routes were not configured to run with the Edge Runtime:
01:52:20.143    ⚡️       - /_not-found
01:52:20.143    ⚡️       - /index
01:52:20.143    ⚡️       - /login
01:52:20.143    ⚡️       - /settings
01:52:20.143    ⚡️       - /users
01:52:20.143    ⚡️       - /websites/[id]
01:52:20.143    ⚡️       - /websites
01:52:20.144    ⚡️ 
01:52:20.144    ⚡️     Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144    ⚡️       export const runtime = 'edge';

01:52:20.142    ⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
01:52:20.142    ⚡️ 
01:52:20.142    ⚡️     The following routes were not configured to run with the Edge Runtime:
01:52:20.143    ⚡️       - /_not-found
01:52:20.143    ⚡️       - /index
01:52:20.143    ⚡️       - /login
01:52:20.143    ⚡️       - /settings
01:52:20.143    ⚡️       - /users
01:52:20.143    ⚡️       - /websites/[id]
01:52:20.143    ⚡️       - /websites
01:52:20.144    ⚡️ 
01:52:20.144    ⚡️     Please make sure that all your non-static routes export the following edge runtime route segment config:
01:52:20.144    ⚡️       export const runtime = 'edge';

JJakov NO [sad](https://cdn.discordapp.com/emojis/1046808820514566274.webp?size=48&qual...

F

fluf•10/26/24, 4:44 PM

not the vencord emoji

F

fluf•10/26/24, 4:55 PM

AWS Amplify seems to solve this issue

F

fluf•10/27/24, 2:14 AM

Why are pages needing a runtime

F

fluf•10/27/24, 2:14 AM

They're not even routes

F

fluf•10/27/24, 2:14 AM

J

James•10/27/24, 10:37 AM

Yes they are

W

wildcat•10/27/24, 4:42 PM

QQ: How to use

crypto

crypto

in next.js on workers? I found if I use

edge

edge

runtime,

crypto

crypto

X509Certificate would be available

B

byoungz•10/27/24, 10:00 PM

Hey everyone, I have a headless WordPress setup I'm deploying to pages. I'm trying to figure out how to add a hook to my account that is using

next-on-pages

next-on-pages

and a

wrangler.toml

wrangler.toml

so that when I publish a new post, it makes a build with the new post. I know how ot make the hook with WP and such, but don't see a way to add it to my account. I also don't see a way to connect my github to account since I'm deploying with the deploy command.

Anyways, how can I connect my github so that when branched ar emerged into main, it deploys

how can I add a hook to my account so everytime I make a new published post, it builds?

Thanks in advance!

Bbyoungz Hey everyone, I have a headless WordPress setup I'm deploying to pages. I'm tryi...

F

fry69•10/27/24, 10:04 PM

Last I checked WordPress is written in PHP, Cloudflare Pages does not support running PHP, so you can use Cloudflare only as front end for where ever you host your PHP site. Next on Pages refers to Next.js
Or am I missing something?

B

byoungz•10/27/24, 10:08 PM

Yeha sorry, I'm bad at explaining. I'm using

@cloudflare/next-on-pages

@cloudflare/next-on-pages

to deploy my site and didn't connect it to github. I wanted to create a hook, like this https://developers.cloudflare.com/pages/configuration/deploy-hooks/#wordpress

However, I don't see a way to add hooks to my pages project using

@cloudflare/next-on-pages

@cloudflare/next-on-pages

but see it them if I set up pages connecting to github account.

I

ItsWendell•10/29/24, 3:41 PM

For people interested in

unstable_after

unstable_after

support with next-on-pages, it just required

waitUntil

waitUntil

which I managed to inject into it:

https://nextjs.org/docs/canary/app/api-reference/functions/unstable_after

https://gist.github.com/ItsWendell/2413b1932d365ee6b3edccef879c589d

K

Kimitri•10/30/24, 6:06 AM

I have a question. I will start a new personal nextjs project, my plan was not use nextjs as a backend, instead I would create an API with workers and bun, my question is, nextjs hosted on cloudflare when I use some server side function to fetching some date from a bun api hosted in cloudflare workers too, is it redundant? Because I don't know if server side functions on nextjs with next-on-pages are the same as a bun API with workers. I don't know if in this way I was making something like double requests that would like reduce the free tier from Cloudflare

Hhsnilsson Might be hard for me to phrase it for you (it means that note would include a st...

E

Epailes•10/30/24, 9:16 AM

Makes sense as open next will get support from multiple orgs, and I think the long term direction at cloudflare is to combine workers/pages into one product anyway

Thanks for the heads up, I'm just going to chill on my current working versions and I'll move over when things stabilise.

Not quite my question. I have real workers indirectly associated with the nextjs api handlers writte

Similar Threads

Similar Threads

Similar Threads