ohh so just like according to nextjs official docs? like just put at root level `middleware.ts`?
ohh so just like according to nextjs official docs? like just put at root level
middleware.ts
Dyes, exactly 
0aite aite, thanks so much, just another question, so if i'm doing static instead, i can use
functions/You can see an example of a
middleware.tsnext-on-pagesGitHub
very simple nextjs apps used to manually test next-on-pages, until we find a better solution - dario-piotrowicz/next-apps-for-testing
0Wow that's cool, thanks a lot sir 
Dyes, but then you can't use Next.js' server features
Dso you can either do: Static Next.js with
functions/functions/unless you have some specific concerns/reasons you should just go with the full stack solution
Dmy pleasure 
Thello. I just try and get service binding work with next-on-pages. my question is is it correct the second worker will be execute asap when using service binding, no network ahead or latency when compared to normal http request.
Tfor the service binding: can we use honojs package to write the worker code, because the .env.MY_SERVICE.fetch explicitly use fetch method on the Worker. With hono, it looks smthing like this: app.get, app.post so there is no fetch expose here.
HHono does expose app.fetch
H
KI'm not sure if the actual issue is https://github.com/cloudflare/workers-sdk/issues/1074, but when following https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/ with git integration, the initial deployment always does not work because either nodejs_compat is not settable in the new pages with git wizard in the web console, or the wrangler setting is ignored as in the bug. It is not a huge deal to push another change to do a new deployment after adding the setting, but wondering if there is a change that can be done to the starter template to address this.
KIt seems like it should be addressable on the web console side because I'd expect it to be done when selecting the "Next" pages configuration in the new git pages app dialog.
D@Kris if you create your Next.js app via C3 and deploy it (still via C3), the flag gets set for you by C3 (which makes an API call for it)
But anyways since now Pages supports wrangler.toml I'm guessing we should be able to add the flag to the template toml file and that should just get picked up.... I'll have to check
But anyways since now Pages supports wrangler.toml I'm guessing we should be able to add the flag to the template toml file and that should just get picked up.... I'll have to check
Btyepscript?
KOk. I am just getting started and have recreated apps a few times. For some reason I'm currently under the impression that using the CLI deploy doesn't create a git integration, and the git integration isn't possible to add later. If you want git integration need to create a new pages app from scratch as far as I know/encountered.
BDyes, unfortunately currently you can't add the git integration after having done a manual CLI deployment 
HI just screenshotted the docs
Kgood morning guys. I have a trouble, I'm trying to deploy a Nextjs application on Cloudflare following the documentation, and to do it I need to install da package @cloudflare/next-on-pages, the problema is this package in the current version 1.11.0 have 6 vulnerabilities, 3 low and 3 moderate. Take a look
Kthe way that I tried to fix it is by installing the vercel package version 32.3.0 bit it maintain the 3 low vulnerabilities, and when I update the vercel package to latest version 33.6.3, the 3 moderate vulnerabilities come back, have some one experienced this issue?
Many way for me to use nodemailer
Mhad just fixed all my errors to find out i cant use it
Mi will have to figure out how to use functions tomorow then at some point it seems
Jthe 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:
