Could you try a deployment with 1.10.0 by any chance? See if there might be a regression in 1.11.0?
Could 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
M
JXD
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 will bundle them into a single file, and then deploy it as a single entity to 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 ?
JIf you want to use
@cloudflare/next-on-pages, your api endpoints should Next.js API routesTperfect, thanks
Shi! Is there a way to get next-on-pages to generate source maps of its webpack files? ie.
__next-on-pages-dist__/webpack/62d6966c94b522734ceb09853b489431.js. I can only seem to generate sourcemaps for the layer before it, ~/_next/static/chunks/1249.d9777ee89355e4b6.js, which is not reported in stack traces when an error is thrown.
Dno, sorry the source maps next-on-pages story is unfortunately very weak at the moment 
SGitHub
Description Unclear to me if this is supported or not at the moment, but wanted to flag it in case not. My error handler, Sentry, needs source maps to map the minified stacktraces to my repo source...
Dyes that's a good summary of it
DI can't really say that it'd be impossible, but most definitely quite the effort
SMost of my next js endpoints are a separate trpc package, so I think I’ll just wrap them in a separate worker and point my app to a separate subdomain to improve error reporting (I have mobile clients too using the next APIs)
TSo, I'm wanting to use Drizzle + Turso DB. Are there any specific gotchas I need to be aware of with cloudflare pages or can I just initialize the db, query it in the api route as if it was a next app NOT on pages?
DI can appreciate that not having it is a significant impairment for development... maybe we should investigate it more in the future, I would likely not try to do that before we start adopting the turbo output (after 
vercel build supports it, that's it), as that will most likely force us to make changes in how we build the worker, so we wouldn't want to have to (try to) solve the source map twice SYeah it’s a significant issue for my use case. Pretty hard to debug production at the moment. Also not having Logpush on pages is hard.
Wit seems there is problem on deployment today, first i got "Deployment complete! Take a peek over at https://*****", but when i visit the url, I got "Nothing is here yet. If the project exists, it may not be ready yet. Please check back later". The depolyment is failed without any detail information
Vgot a silly question, that i dont see any answer, in the web, why there is a static sites, everywhere, on the cloudflare, pages, does this not work if i have a SAAS product that will interact with workers, and generate SSR page.? its in sveltekit btw im confused,
IThere's 2 main types of sites (and some are a combination of both):
- Client side rendered, also known as CSR. This is raw HTML/CSS/JS. The browser uses JavaScript to "hydrate" the content of the page, or loading things on the page (i.e. like an ecommerce store with filters for products or a counter incrementing when the user clicks the button).
- Server side rendered, also known as SSR. In this case the server (Cloudflare Pages in this case) renders out the HTML based on the request, so that by the time the response arrives at the browser it's already rendered and complete. Pages only supports SSR with JavaScript, not with any other server like C#, and only with specific frameworks like SvelteKit or Astro.
IAnother example would be Amazon. You'll notice that as soon as you load the page the products are visible (SSR) but then when you change a filter the products change without a full page reload (with JavaScript on the browser).
Vso bascially no client side js right...?
IClient side JS is fully possible.
ISvelteKit will automatically convert your
.svelte files to JS for you though.ISo you just write Svelte as normal.
IA static site just means not server-side rendered. It can still be interactive and have client-side JS.