<@94508156243161088> Hope you don't mind that I ask so directly and don't feel offended in any way:

@James Hope you don't mind that I ask so directly and don't feel offended in any way: Would you rate the current NextJS on CF Pages solution "stable"? I need to ask as either we had bad luck, bad timing or both. Developer Experience feels off with the undebuggable 1101 error. But this might be a general CF worker thing though ( https://github.com/cloudflare/workerd/issues/210 ) ?
Having a very basic NextJS app and not being able to get it running on CF was quite frustrating. Especially as it works on Vercel. On the other hand it is our first NextJS on CF Pages PoC. So we do not have experience or other data points regarding issues or "smoothness" of it.

GitHub

Improve "The script will never generate a response." debuggability ...

The The script will never generate a response. error is generally a very hard error to debug, the only source on the internet being this blog post. We recently had this issue thrown on rare occasio...

JJames i'll ping dario

JThielOP•5/9/24, 8:40 PM

Thank you. I will recheck tomorrow for a newer version and try that

JJThiel <@94508156243161088> Hope you don't mind that I ask so directly and don't feel o...

James•5/9/24, 9:22 PM

Generally yes. This error is very rare

James•5/9/24, 9:23 PM

1.11.3 should be available on npm now

Mackenly•5/9/24, 9:26 PM

With Baselime, is there any integration with next on pages? In their docs it seems like all it does for pages is capture logs and it has to be instantiated and "flushed" in each function to be able to do that. Since it got acquired by CF, I figured I should start learning it, but it seems pretty limited in functionality unless I'm majorly missing something. Anyone able to shed any light?

TThomas Any chance 1.11.3 has the requestinit dict cache kerfuffle fixed 🙂

James•5/10/24, 7:31 AM

not yet, something funky is happening in that pr that I'm going to look into this weekend

JJames 1.11.3 should be available on npm now

JThielOP•5/10/24, 8:32 AM

So bad luck and bad timing

It looks like 1.11.3 actually did fix the issue we encountered. After redeployment with an updated package.json and the most recent NodeJS LTS version it works as expected. Thank you very much.
So rule of thumb: Whenever we encounter the 1101 error: Call for help here?

James•5/10/24, 8:48 AM

GitHub issue on the next-on-pages repo ideally, both Dario and I will see it. in this case thankfully the person who reported the issue also managed to figure out the cause, otherwise we probably wouldn't have been able to find it

mau•5/10/24, 8:54 AM

When trying to deploy it is forcing me to use edge runtime, even though i have made dynamic false

here is link to github issue which was reported by someone else

https://github.com/cloudflare/next-on-pages/issues/745

GitHub

[🐛 Bug]: Dynamic Pages / Routes can't deploy to Cloudflare Pages · ...

next-on-pages environment related information Relevant Packages: @cloudflare/next-on-pages: 1.11.0 vercel: N/A next: 14.1.4 Description I'm currently building a website with Next.js 14 and Pris...

mau•5/10/24, 8:54 AM

I am also generating meta data just like this example

Llaurent -> Just throwing it out there, my honest feedback on my cloudlare experience. I...

laurent•5/11/24, 5:36 AM

Update: I think I've got the Next.js app in a satisfying state:

Moved most server components and server action "magic" to good old client components with api routes HTTP calls from the user's browser.
- The data flow just makes more sense mentally, and it gives you a chance to test backend logic from outside the nextjs app (with postman for example).
- With Tanstack Query client side you can also retry queries if they go wrong or while waiting for a database update for example.
Moved the critical and hard to debug Stripe payment logic to standalone (different project) workers. I now have 2 stripe webhooks workers waiting for POST calls from stripe, one in stripe test mode, one in stripe live mode. Having a deployed test mode worker that is bound to a deployed D1 database was key for my debugging. D1 was rejecting writes because of a foreign key constraint (I was passing the wrong id).
Enabled logpush for the standalone workers (don't forget to add `logpush = true` in wrangler.toml after enabling logpush in the dashboard). Now my logs are persisted and I can go check what went wrong in prod for these critical workers.
Next step, looking for a simple way to access / read / sort / filter the log.gz files that are on R2. Is there an app that makes it simple? Or are most people using command-line jq as specified here? https://developers.cloudflare.com/logs/tutorials/parsing-json-log-data/

At the end of the day the mistake was mine, and I would like to apologize for my earler negative comments, but some extra and persistent logging (on D1 operations, on cloudflare pages, on cloudflare pages workers) would really help people like me coming from vercel and switiching to the cloudflare ecosystem.

Llaurent Update: I think I've got the Next.js app in a satisfying state: - Moved most se...

laurent•5/11/24, 6:09 AM

https://x.com/laurentlahmy/status/1789172109442154783

39dylan•5/11/24, 10:20 AM

looking for advice on how to structure a "white-label" monorepo-ish website that has:

base template/starter repo that includes ui components, middleware, auth etc (essentially everything except website content)
child website/content repos are built with the above foundation and have their own configuration/content/components
changes to base template should ripple and update for all child websites
my current issue is cf pages only allows you to use a github repo once (5 times if it is a monorepo) so i want to avoid doing some weird git submodule trickery. any advice how i should proceed?

rob•5/11/24, 2:30 PM

@jjjrmy didn't you do something similar with Astro?

Llaurent Update: I think I've got the Next.js app in a satisfying state: - Moved most se...

James•5/11/24, 6:04 PM

no need to apologize, they were valid criticisms/frustrations

loco•5/12/24, 10:00 PM

is it possible to use a service binding while developing locally(next dev) to a worker that is already deployed?

TThomas Hey James, any luck? Anything I can do to assist?

James•5/13/24, 5:25 PM

Anything I can do to assist?

delete our e2es

James•5/13/24, 5:42 PM

basically it doesnt make any sense why they're failing for a middleware test

James•5/13/24, 5:58 PM

oh crap

James•5/13/24, 5:59 PM

i found it and it's a big oopsie

James•5/13/24, 6:50 PM

i believe it should all be fixed now, dario will likely have a look tomorrow

James•5/13/24, 7:43 PM

MetalGear•5/13/24, 8:20 PM

What features am I losing moving my next 14 web app from vercel to cloudflare

James•5/13/24, 8:35 PM

https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/docs/supported.md is probably a good place to start for reference

real_witt•5/14/24, 12:52 AM

I've looked around the documentation and am struggling a bit, is there anything extra you need to do to render a Cloudflare function on a path besides create a file in the

functions

functions

directory? I have a simple

helloworld.ts

helloworld.ts

that returns the documentation example

helloworld.ts
export function onRequest(context : any) {
  return new Response("Hello, world!")
}

helloworld.ts
export function onRequest(context : any) {
  return new Response("Hello, world!")
}

but when I run

npm run dev

npm run dev

and visit

/helloworld

/helloworld

I don't see the hello world text. worrySadder

James•5/14/24, 5:53 AM

the functions directory does not work with next-on-pages as we generate our own worker for your app. you should be using nextjs API routes

real_witt•5/14/24, 10:34 AM

Thanks! That clears up some confusion for me.

real_witt•5/14/24, 10:37 AM

Me learning Cloudflare pages lol

TThomas Hey James, any luck? Anything I can do to assist?

James•5/14/24, 10:25 PM

we're going to park it termporarily because i'm concerned it might interfere with how nextjs fetch caching works, since this is to fix an issue in the react fetch patch which is a layer deeper than the nextjs fetch patch i believe

TThomas Any idea how i can work around it without moving to vercel temporarily and playi...

James•5/14/24, 10:27 PM

if you want to use the changes in this pr, you can use the prerelease linked in it

James•5/14/24, 10:27 PM

https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/9067847845/npm-package-next-on-pages-771

https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/9067847845/npm-package-next-on-pages-771

James•5/14/24, 10:29 PM

you can change it to

npx https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/9067847845/npm-package-next-on-pages-771

npx https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/9067847845/npm-package-next-on-pages-771

and it will build using the build for this pr

James•5/14/24, 10:30 PM

sounds good

NNob okay, I enabled smart placement yesterday and got the errors yesterday and today

SM•5/15/24, 4:53 AM

Did disabling "smart placement" fix the internal server error for you? I ask as we're having the same issue but we don't have smart placement enabled at all. Wondering if it's something else? Our issue seems to be very random, almost like it's capacity related (too many hits in a short amount of time).

SSM Did disabling "smart placement" fix the internal server error for you? I ask as ...

Nob•5/15/24, 8:25 AM

yes it did

NoWay•5/15/24, 2:05 PM

Hello everyone,
I have a problem uploading my nextjs application in cloudflare using the build command for "normal nextjs" / not static nextjs. I have some dynamic paths / routes where I'm using some server built-in packages (e.g. crypto / http / etc...). Cloudflare requires me to put