MI can't login (?) 
MMbrowser sends me to localhost and then I get a localhost refuses to connect
Mok strange apparently arc blocks that for some reason
Jlol
Mworks in safari tho
Mhow do you specify the deployment for preview?
Jit will choose the latest deployment by default
Jhere ya go
Mahhh you legend
Mthis hurts me 
Jwell that isn't what i wanted to see XD
M 
MI've got to run off and do something else rn, but I'll be back in a couple hours hopefully the magic 
will have fixed it by the time I'm back, otherwise I'll create an issue in
hopefully the magic will have fixed it by the time I'm back, otherwise I'll create an issue in pages-helphuh, odd, requests to _next/image are throwing an exception
Jthat is pretty strange
MOn my website?
JYes
M:0
JCould you try a deployment with 1.10.0 by any chance? See if there might be a regression in 1.11.0?
Jand if 1.10.0 works, try 1.11.0 again just for the sake of it
MKk I’ll give it a go once I’m back
Jno worries
M1.10.0 works
Jnow please try 1.11.0 again just to confirm 
Mso
Mthat also works
MJXD
Jwelp
Myes. agreed.
JI ended up reporting https://github.com/cloudflare/next-on-pages/issues/722, as I think if solvable it could help mid/large projects move successfully to Cloudflare. I wasn't able to trace the issue, as I do see the routes being lazy loaded perfectly (e.g.
If anyone's have any ideas or things worth trying, I'm happy to try it out! Thanks!
await import(item.entrypoint)) but can't really see what wrangler is doing internally (tried --no-build with an upcoming fix and also debugging internally and couldn't really see anything wrong, route-specific code seems to be only in additionalModules, etc.).If anyone's have any ideas or things worth trying, I'm happy to try it out! Thanks!
PHey, anybody have the experience of doing queries on firebase / firestore during build with next on pages?
PI mean build pages server side from firebase database data collections
TSo I was interested in using Hono as my api handler instead of using nextjs but i got to thinking, if i'm running nextjs on cloudflare pages, won't my route handlers run directly on cloudflare workers? So is there any benefit to replacing the built in api handlers with Hono other than convenience and portability? I don't plan on hosting my backend separately unless i really had to and the organization is whatever i'll get used to the file based routing.
TI have a question: When I use next-on-pages for my NextJS app. I have some API Route Handlers in my next app. is it correct that next-on-pages will create a seperate worker for each API route handler when I deploy my nextjs app to Pages using next-on-pages?
HNo.
next-on-pages
PI asked that previously, you can read Dario’s answer it’s not needed with next-on-pages
Tbundle everything into a file and seperate, do you think it will affect the performance?
HNo, since none of the code is actually executed unless that route is triggered
Tthank you
Dit's not all bundled into a single file but yeah all into a single worker 
HOh interesting, it does dynamic imports?
THi Dario. do you think if I use Nextjs API route handler or I write and deploy the seperate worker for each APi route handler. do you think which one is more performance and cost-saving.
D
GitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
Da separate worker for each api route handler seems very very cumbersome to maintain, and it would likely incur more cold starts than a single next-on-pages worker
so I would not go that route personally
performance-wise it should be practically almost the same (besides the issue mentioned by @juanferreras above (https://discord.com/channels/595317990191398933/1135899572141568050/threads/1221910415169294518), which can add some minor slight slowdowns
)
cost-saving I can't imagine there being any difference
so I would not go that route personally
performance-wise it should be practically almost the same (besides the issue mentioned by @juanferreras above (https://discord.com/channels/595317990191398933/1135899572141568050/threads/1221910415169294518), which can add some minor slight slowdowns
)cost-saving I can't imagine there being any difference
Discord
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
TThank you very much Dario
Dno problem
THello, so I'm trying to integrate Turso DB and I just wanted to ask about best practices as all the examples I've found are really specific how to setup an individual worker with turso. I know functions are workers under the hood but I guess I'm getting a bit confused of the best practice to fetch data. Should I be creating api endpoints in the /api folder OR /functions? or _worker ?
