the name nodemailer implies that it's designed specifically work in nodejs so it'll likely have inco
the name nodemailer implies that it's designed specifically work in nodejs so it'll likely have incompatibilities with the edge runtime
Myes i wasent really thinking that far ahead tbf
Mi dont think there is anything else that can take a email login e.g. SMTP creds and send out a email though it locally
Ghey, i was wondering if anyone has had any success migrating from vercel to cloudflare for their next.js 14 project. i am looking to do so as i use cloudflare for other parts of my project and cloudflare is nice and cheap. However, I was wondering if cloudflare fully supports all the features that next.js uses?
JWe have a supported doc that I would recommend giving a quick look. The notable call outs are that we are not able to support Incremental Static Regeneration or Partial Prerendering due to limitations around how they work (they depend on nodejs).
VHey all, for local development I'm seeing that I can now just call
This is quite amazing, but I'm trying to figure out how to enable connecting to real remote objects instead of a mocked version (through miniflare). Something equivalent to this wrangler command:
Is there a way to enable the
next startThis is quite amazing, but I'm trying to figure out how to enable connecting to real remote objects instead of a mocked version (through miniflare). Something equivalent to this wrangler command:
npx wrangler dev --remoteIs there a way to enable the
--remotenext startthanks james
JAfraid not since the next dev bindings are using miniflare which is local-only emulation
VIt seems like it should be possible in theory:
https://developers.cloudflare.com/workers/testing/local-development/#develop-locally-using-remote-resources-and-bindings
Isn't next-on-pages using wrangler underneath?
https://developers.cloudflare.com/workers/testing/local-development/#develop-locally-using-remote-resources-and-bindings
Isn't next-on-pages using wrangler underneath?
Cloudflare Docs
Develop your Workers locally via Wrangler.
V"wrangler dev runs locally by default. This means that all resources and bindings are simulated locally as well. However, there may be times you need to develop against remote resources and bindings. To run wrangler dev remotely, add the --remote flag"
VWhat I'm running into -- our app uses a mix of R2 bindings and the aws presigned urls which makes it tricky to test the app as-is
JIt uses the getPlatformProxy() utility that ships with wrangler and that utility uses miniflare's magic proxy internally, so it's a bit different to just running wrangler dev
VAh got it thanks for clarifying
Is there a workaround to test things out such as running the next-on-pages with wrangler instead of using
Is there a workaround to test things out such as running the next-on-pages with wrangler instead of using
next startYou can build your app with next-on-pages and then run it using wrangler pages dev if you wanted to run things in wrangler, but for development this is not advised as you'd lose out on HMR
Vgot it
Vmaybe i need to implement a local version of pre-signed urls
VMaybe it's a large undertaking - feature request would be to allow a remote option for setupDevPlatform 
certain features are tough to test without the real thing
certain features are tough to test without the real thingVI guess it means getPlatformProxy would need to somehow transparently proxy to real bindings vs miniflare. Seems complex but would make the developer experience amazing
VGitHub
Describe the solution Currently, unstable_dev supports passing in a local flag in the options object, but getPlatformProxy doesn't support it. This means that things like Cloudflare AI, which r...
VOk so looks like it's really on getting that implemented since I'm seeing that
setupDevBindingsIndeed
WHello! So I’m using next-intl for my NextJs site, it’s my first time using Cloudflare, so now that I deployed with Git… well the page shows a 404 error saying it doesn’t exist, I’m not sure if I need to like use functions to make it work with next-intl or something (or if the problem is even related to next-intl lol)
FQuestion about caching and SSR pages.
Our assumption was that when we fetch data on any page, Next.js's data caching would kick in.
However, with
I understand that SSR pages are... Server Side Rendered.
But our use case is that not everything needs to be fetched at request-time.
Specifically, the data we fetch from Firestore only needs to be fetched at build time, the data we do want to fetch on every request comes from Supabase.
How can we use the cache on an SSR page?
Our assumption was that when we fetch data on any page, Next.js's data caching would kick in.
However, with
export const runtime = "edge"I understand that SSR pages are... Server Side Rendered.
But our use case is that not everything needs to be fetched at request-time.
Specifically, the data we fetch from Firestore only needs to be fetched at build time, the data we do want to fetch on every request comes from Supabase.
How can we use the cache on an SSR page?
RHow can I use Sentry Pages Plugin with Next?
Nif you fetch your data you can do:
N?
P
PFYI : It's a long journey for Felix, and Philippe and I we all work on the same project
NI think "force-cache" is self explaining of its function
Ni dont understand your question
Pnot a question, I meant thank you it seems to work
Nahhh okay long journey for me too 
P2 days of searching and then the trex head solves it with 2 words
Nalso you should add a KV binding named
__NEXT_ON_PAGES__KV_SUSPENSE_CACHEbecause without it, caching is only at datacenter level
SYeah, the binding was already in place but no keys were saved before the force-cache 
NNi'm doing gaming websites
FThanks a lot though, seriously.
JIIRC force-cache is supposed to be the default but I guess we probably need to do some logic to apply it if no cache value is specified.
I'd be a bit hesitant to add that in now though considering we've had our fetch cache live for like 8 months and that kind of change would probably be breaking for a lot of users
I'd be a bit hesitant to add that in now though considering we've had our fetch cache live for like 8 months and that kind of change would probably be breaking for a lot of users
Jit's one of those things that would technically be a bug fix but in actuality would be a breaking change for almost all users who use fetch on the server
Pcould be added to documentation 
PHey Nob, if you ever find yourself in Sherbrooke, QC, Canada, hit me up, free beer on me!
Nahah, France is a bit far from Canada but maybe in 10 years x)
NI forgot I'm not even old enough to drink
NPlà je comprends pourquoi tu ne comprenais pas quand je parle comme Yoda 
Mhey where do i put my functions for the cloudflare pages plugins
Mis it in the root dir or should i put inside /src or /src/app
N/app/api and you create api routes
Mcool
