-> Just throwing it out there, my honest feedback on my cloudlare experience. I tried to go full cl

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

I tried to go full cloudflare for my project https://fullwindcss.com/

I learnt it's called cutting edge because it will cut you

I went with

nextjs (next-on-pages) app router, server components, server actions, edge runtime
drizzle + D1 for database

OK:

all the static parts work fine.
if you have a blog it will be great and free up to 1mb for your site's bundle which is turned into a worker function. I was just over 1mb and had to switch to workers paid for 5$ a month (which is very fair)
you get the benefits of serverless, the site can handle usage spikes without you having to worry about anything (non issue during the product hunt launch).

MEH:

Next Auth on Drizzle + D1 + edge runtime has been a challenge (but manageable). Examples in the repo are much nicer than the documentation

NOPE:

Stripe payments that work in dev fail most of the time in prod. I tried to move from server actions to webhooks, still doesn't work and basically impossible to debug.
Error logs can be super cryptic, like "Error: The script will never generate a response."
you can't use cloudflare pages' sentry plug-in in a next-on-pages app, so no error reporting.
Log retention is not possible at the moment. You can either stream from your terminal or from the web dashboard. Good luck debugging prod in these conditions.
The team at cloudflare isn't super dedicated to next-on-pages. It's not a core product the way it is at Vercel. Github issues can stay unanswered for 2 weeks, and sometimes for ever. The Discord server is more active.

All things considered, I'm going to move away from a full next-on-pages app.
Maybe a mitigation is to use classic workers (not edge runtime nextjs api routes) to handle the backend? Hope Stripe works there.

I would have loved to have a great experience on cloudflare but we're not there yet.

fullwindcss

Build better apps with the whole tailwindcss color palette

WarlockJa•5/8/24, 12:27 PM

@laurent Hello. Can you provide a link to the repo example, you've mentioned, about "Next Auth on Drizzle + D1 + edge runtime". This is exactly the problem I am struggling at the moment.

WWarlockJa <@329986722823667714> Hello. Can you provide a link to the repo example, you've ...

laurentOP•5/8/24, 1:22 PM

My repo is private but happy to jump on a call and show you

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

James•5/8/24, 5:43 PM

Error logs can be super cryptic, like "Error: The script will never generate a response."

This would be a bug that generally you should open an issue on our repo for. Another user raised an issue a couple days ago about this that we have fixed related to the fetch patch which may also solve the problem for you - I'll shoot dario a message about making a release.

Github issues can stay unanswered for 2 weeks

Please feel free to bump an issue or add additional context if it's also affecting you.

WWarlockJa <@329986722823667714> Hello. Can you provide a link to the repo example, you've ...

laurentOP•5/8/24, 6:18 PM

just re-read, I meant the next auth repo, examples folder https://github.com/nextauthjs/next-auth/tree/main/apps/examples/nextjs
I think I also took inspiration from another repo, this one I think https://github.com/yongyi520/cloudflare-nextjs-d1-error
still happy to show you how I did it

James•5/8/24, 7:05 PM

it's due to some logic in the react server code which is what i'm trying to hack around in that pr, although we're seeing weird behaviour with the e2es which i need to spend some time looking into

James•5/8/24, 7:05 PM

i believe it's a relatively recent thing (past few months)

James•5/8/24, 7:20 PM

if you wanted, you could even try using the prerelease in the PR to build with

JThiel•5/8/24, 8:38 PM

Hey there, looking for some help regarding some nasty and close to impossible to debug Error 1101 "Error: The script will never generate a response." errors.
We are developing quite a simple NextJS app that's bringing some APIs together. In particular we use Auth0 as an Auth Provider and then SWR to fetch data from multiple REST routes. Classic Customer Portal solution. It's still in the PoC level so we didn't even leverage KV or D1 yet. What drives us crazy is the fact that the same code runs perfectly fine on Vercel but constantly hits the 1101 on CF Pages.
We tried to run

wrangler pages dev

wrangler pages dev

locally in hope that it might give us some more information but it simply won't work on our Windows machines.
If anyone have some ways on how to demistify this generic error ... I am highly greatful.
For context: We had some issues in one of the dependencies of the project before. That was when we first deployed it to Vercel. Vercel gave us a perfect clear logging output regarding the issue. We fixed that library to make it Edge compatible. Not the app runs fine on Vercel but still not on CF Pages.
We have auto Github deployments configured on both platforms and use the same config (ENV vars) on both. So code and config are identical. It's just the platform that difers ...

TThomas prerelease for next-on-pages package itself right?

James•5/8/24, 10:20 PM

the prerelease link in the pr - https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/8953244999/npm-package-next-on-pages-771https://prerelease-registry.devprod.cloudflare.dev/next-on-pages/runs/8953244999/npm-package-next-on-pages-771.

we don't have a canary. the beta release has a recursive fetch patch bugfix but nothing for the cache property

James•5/8/24, 10:20 PM

if your stuff is working with the beta release, it's probably not fixed the problem, but just luck

James•5/8/24, 10:22 PM

yeah that'll be the beta which has a recursive fetch patching fix, completely unrelated to cache property on requestinit

TThomas have you tried looking at compatibility flags? https://developers.cloudflare.com...

JThiel•5/8/24, 10:52 PM

This is part of the

wrangler.toml

wrangler.toml

for the project:

compatibility_date = "2024-04-23"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

compatibility_date = "2024-04-23"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

With this in the ENV Var:
NODE_VERSION="20.12.2"NODE_VERSION="20.12.2"

JJThiel Hey there, looking for some help regarding some nasty and close to impossible to...

James•5/8/24, 11:43 PM

please can you try with the latest release. another user reported an issue causing this that has been fixed. it's possible you are running into the same bug that they were.

JJames please can you try with the latest release. another user reported an issue causi...

JThiel•5/8/24, 11:47 PM

Hey James, sure, would love to! Can you be a bit more precise about the latest release of what exactly you refer to?

JJThiel Hey James, sure, would love to! Can you be a bit more precise about the latest r...

James•5/9/24, 11:15 AM

the latest release of @cloudflare/next-on-pages

JJames the latest release of @cloudflare/next-on-pages

JThiel•5/9/24, 8:12 PM

We are already on @cloudflare/next-on-pages 1.11.2. Or do you suggest to use a git branch / commit?

James•5/9/24, 8:14 PM

oh damn

James•5/9/24, 8:14 PM

it looks like the release last night failed to publish to npm

James•5/9/24, 8:14 PM

argh

James•5/9/24, 8:14 PM

i'll ping dario

JThiel•5/9/24, 8:39 PM

@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

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

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

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

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

-> Just throwing it out there, my honest feedback on my cloudlare experience. I tried to go full cl

Similar Threads

Similar Threads

Similar Threads