PGitHub
A lightweight JWT implementation with ZERO dependencies for Cloudflare Workers. - tsndr/cloudflare-worker-jwt
TI have a next-on-pages API need to call other Worker. Is it similar when useing binding and fetch method for calling other Worker from next-on-pages application.
Nid assume just fetch()
Dyou need to set up a service binding to your Pages application to a worker, then you can access the binding with
getRequestContext and use its fetch
TCan I just setup a new worker. Deploy to Cloudflare. That worker has a url. On my page I just use fetch with that url like a normal url.
TI am not sure which one is a best practice. Since both of them still work
HService Bindings are best practice, since they are faster, plus they also prevent anyone else from accessing the second Worker
Dhave you tried the version without the binding? as far as I know that shouldn't work...
Nmade my first nextjs page on cloudflare pages, with working db and auth :D
0has anyone gotten middleware to work in pages with nextjs?
0do you name it normally at the root of your project
middleware.ts? or create it under functions/_middleware.ts?0a bit confused hahah
DHi @0xwei_hup 
are you trying to create a full stack Next.js application?
or a static Next.js application with some server side logic implemented with
are you trying to create a full stack Next.js application?
or a static Next.js application with some server side logic implemented with
functions/?0full stack next.js 
Dah ok, so you should use a proper
middleware.ts Dand please keep in mind that
functions/ is incompatible with next-on-pages, you cannot use those at all 0ohh 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/?DYou can see an example of a
middleware.ts being used with next-on-pages here: https://github.com/dario-piotrowicz/next-apps-for-testing/tree/master/apps/middleware-13.2.4GitHub
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/ or full stack Next.js without functions/ Dunless 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 start and it magicaly works through this addition: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:
npx wrangler dev --remoteIs there a way to enable the
--remote flag when I call next start ?Gthanks james
JAfraid not since the next dev bindings are using miniflare which is local-only emulation