Workers are now limited to 25MB, not 10.
Workers are now limited to 25MB, not 10.
Toh so 1mb free 25mb on paid?
IYup.
Ttake my $5
Twhy I see on the website it said that the limit is 10MB. Can you share the link for 25 MB limit?
IThere was an open docs pull request but it was closed for some reason: https://github.com/cloudflare/cloudflare-docs/pull/13253/files
ITOn the github it said that 5MB for free and 25MB for 5$, can anyone in Cloudflare team confirm this? On the docs it still showed 1MB and 10MB.
TPrediction: They're going to announce the increased plans as part of this week's dev week announcements. 
JThe 25mb limit has been a thing for quite a long time, not a new plan increase
Tand the free plan limit is 5MB instead of 1MB as docs mentioned?
Jnot sure about the free plan, but paid has been 25 for quite a while
EAny recommended libraries for password hashing in edge runtime. bcryptjs and bcrypt are both not compatible
Twhat i do:
EPerfect thanks haven’t used Lucia but looks good to me
PHey, in order to fecth Firebase Firestore rest API, I want to authenticate with google and obtain a JSON Web Token during build or before build and then fetch my database. It works locally, but can't find a way to make it work on cloudflare, any suggestion on how to do this?
AI've had a failing deployment because my worker was more than 10MB in the past two weeks or so.
TPGitHub
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-pagesohh 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-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/ 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
