is normal that my deploy appear on the pages.dev subdomain but not on the linked domain yet (linked

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

DoggeSlapperOP•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

DoggeSlapperOP•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

DoggeSlapperOP•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

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

@fry69 lol I forgot I used next15 xD

D

DoggeSlapperOP•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

crypto

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

edge

edge

edge

edge runtime,

crypto

crypto

crypto

cryptoX509Certificate 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

@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

@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

unstable_after

unstable_after support with next-on-pages, it just required

waitUntil

waitUntil

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.

V

Victor Berchet•10/31/24, 7:24 AM

Hey,
We have a PR up to support middleware on @opennextjs/cloudflare, check the details at https://discordapp.com/channels/1283128968140161065/1288871672035803236/1301446458352074772

VVictor Berchet Hey, We have a PR up to support middleware on @opennextjs/cloudflare, check the ...

F

fry69•10/31/24, 7:27 AM

Can't check out, it links to another Discord (

# unknown

# unknown

# unknown

# unknown). Can you link the PR on GitHub for context?

Ffry69 Can't check out, it links to another Discord (`# unknown`). Can you link the PR ...

V

Victor Berchet•10/31/24, 7:28 AM

M

micooz•11/1/24, 3:17 AM

Are there any other benefits of migrating from next-on-pages to opennextjs besides being able to use Node.js runtime, like performance, responsiveness?

R

R in Tokyo•11/1/24, 11:03 AM

I’de just like to confirm next on pages can do SSR but not SSG correct?

RR in Tokyo I’de just like to confirm next on pages can do SSR but not SSG correct?

J

James•11/1/24, 5:57 PM

You can do SSR and SSG, but not ISR

Mmicooz Are there any other benefits of migrating from next-on-pages to opennextjs besid...

J

James•11/1/24, 5:58 PM

Long-term support will be for the OpenNext one, and it'll enable better compatibility with Next.js features. next-on-pages will eventually be phased out once the OpenNext adaptor is in a good place.

K

Kimitri•11/1/24, 6:10 PM

I'm about to start a Nextjs project and I want to host it on Cloudflare, but I need to know what in the NextJs app is charged by workers ? The rendered page is charged as one request or the fetch functions is charged as one request?

KKimitri I'm about to start a Nextjs project and I want to host it on Cloudflare, but I n...

F

fry69•11/1/24, 6:11 PM

Static assets do not get charged, functions count as workers (in fact they are workers).

Ffry69 Static assets do not get charged, functions count as workers (in fact they are w...

K

Kimitri•11/1/24, 6:14 PM

so basically fetch functions are charged right?

KKimitri so basically fetch functions are charged right?

F

fry69•11/1/24, 6:15 PM

Not every fetch call of course, but the whole function that calls fetch() must run inside a dressed up worker, that counts as one.

Ffry69 Not every fetch call of course, but the whole function that calls fetch() must r...

K

Kimitri•11/1/24, 6:16 PM

thank you, I didn't know about that

JJames You can do SSR and SSG, but not ISR

R

R in Tokyo•11/1/24, 11:58 PM

I am getting an error with dynamic routes that generateStaticParams… I believe it was working before next 15 … So you’re saying that generateStaticParams should not throw an error?

Specifically starts with next@15.0.0-canary.175 and up.

Edge + generateStaticParams not allowed.

JJames Long-term support will be for the OpenNext one, and it'll enable better compatib...

B

Baran•11/2/24, 8:29 AM

Will there be a migration guide from next on pages to opennext?

RR in Tokyo I am getting an error with dynamic routes that generateStaticParams… I believe i...

J

James•11/2/24, 2:24 PM

Next.js 15 hasn't been tested with it so may have issues

BBaran Will there be a migration guide from next on pages to opennext?

J

James•11/2/24, 2:24 PM

https://opennext.js.org/cloudflare/get-started#5-remove-cloudflarenext-on-pages-if-necessary

JJames https://opennext.js.org/cloudflare/get-started#5-remove-cloudflarenext-on-pages-...

B

Baran•11/3/24, 3:16 PM

Thanks!

N

Nexorsist•11/5/24, 1:43 PM

Hi everyone. So I have a NextJS app (<15.0.0) and was trying to deploy to pages. My has both server and client functions and is still relatively small. While trying to deploy I see the files in /.next/cache are larger than the 25mb limit. Tried to troubleshoot to optimize where I can (don't have many static assets and they're small). Build direct was set to /.next and npm run build as the command. Am I doing something wrong or is it plainly a matter of refactoring everything to use Cloudflare workers?

N

Nexorsist•11/5/24, 1:43 PM

I'm still in early stages of Dev and while I have been deploying onto my local server and serving it up that way, thought it would be convenient to test out Pages instead

B

burguês•11/5/24, 2:43 PM

Subject: Build Failure Due to Bundle Size Limit Exceeded

Hi everyone,

I'm experiencing an issue while deploying my Next.js app on Cloudflare Pages. The build fails with this error:

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

Earlier in the logs, it mentions:

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

It seems my bundle size exceeds the 25 MiB limit. Here's a snippet from the build log:

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

Total (231 modules)                                                                        │      │ 25488.77 KiB │
...
Generated Pages Functions bundle size (26272676) is over the limit of 25.0 MiB

I believe the large number of modules and functions is causing the issue. Does anyone have advice on how to reduce the bundle size or handle this situation? Or how to check bundle size?

Thanks in advance!

HHello, I’m Allie!Pages doesn’t support Crons

M

MarcusAurelius•11/5/24, 4:40 PM

Does the new worker's framework platform have support for cron ? If i have a nextjs app deployed can i add a scheduled trigger to the function ?

Does anyone know how to run a cronjob with open-next cloudflare, nextjs 15 ?

MMarcusAurelius Does the new worker's framework platform have support for cron ? If i have a nex...

H

Hello, I’m Allie!•11/5/24, 4:42 PM

Workers with Assets are also able to export a Scheduled Handler for Crons. As for whether

open-next

open-next

open-next

open-next itself supports it, I am not sure

C

Chapi•11/5/24, 5:20 PM

Hey guys

Was working on nextjs on CF pages and I always use binding on the API side now I wanted to use on server actions and it is saying

only async function are allowed to be used in use server. File

only async function are allowed to be used in use server. File

only async function are allowed to be used in use server. File

only async function are allowed to be used in use server. File but the getRequestContext method is not async I think.

Does anyone knows how to use since I kinda need the bindings to work.

B

burguês•11/5/24, 5:21 PM

Generated Pages Functions bundle size (26282201) is over the limit of 25.0 MiB
Failed: generating Pages Functions failed. Check the logs above for more information. If this continues for an unknown reason, contact support: https://cfl.re/3WgEyrH

How to check bundle side? How to understand which file is causing this?

CChapi Hey guys Was working on nextjs on CF pages and I always use binding on the API...

D

D Trombett•11/5/24, 10:20 PM

Remove the

export const runtime = "edge"

export const runtime = "edge"

export const runtime = "edge"

export const runtime = "edge". It is not needed in use server files

is normal that my deploy appear on the pages.dev subdomain but not on the linked domain yet (linked

Similar Threads

Similar Threads

Similar Threads