so bascially no client side js right...?
so 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.
Vso basically, a full*** sveltekit app should work on page and all the apis goes into workers... and thanks
IExactly, but even beyond that, SvelteKit will automatically convert your endpoints and other server stuff to Pages Functions for you (which is basically Workers).
Vif thats the case, i dont know why people chosing vercel yikes
ISo you don't need a separate Workers API. It's of course possible, but it's optional because Pages will do it for you.
Vreally
Vwow,,... thats even easier...
Vbut question, again, the bandwith is unlimited are you kidding me....
Vwell, ummm like if some one just need to use workers, that creates a sveltekit app with nothing on the routes, but only apis... does that mean he gets unlimted requests tho 
IYes, anything static will be unlimited requests for free.
Vor pages will make them as workers, for us...
IYou might want to use
@sveltejs/adapter-static to make sure nothing server-side is generated though.Vyep already have everything setup....
I(rather than the default
@sveltejs/adapter-auto)Vi should say bye bye vercel 
CHey Guys, I am stuck on this issue while using next-on-pages next-dev module, not able to get local bindings working, (I am currently in process of using t3 stack with next-on-pages & d1 as database)
SIs it possible to get a flag like wrangler dev's
--remote
JAfraid not, the bindings in next dev are emulated using miniflare, so it's local only
PTrick question, We need a page to query Supabase on edge workers (SSR style) based on url parameters. That page needs to use a layout which fetches data from Firestore at build time. We do not want to fetch Firestore with the workers.
How can we mix a statically generated layout at build with dynamic page components generated by Edge?
How can we mix a statically generated layout at build with dynamic page components generated by Edge?
THi everyone, I have a question: I have a nextjs that use next-on-pages to deploy to Pages. is there anyway I can use wrangler to build _worker.js and then deploy it to Workers. I can not use the npx vercel build because the webpack has some issues with one of my library.
Ti try to use node-postgresql library in next-on-pages
NHi, I randomly get 500 Internal Server Error when going to my ssr streaming nextjs website, I dont find any other error
N
Nsometimes I get the error 3 times in 1 minute and then I can't get it once in hours
JIf you tail your deployment with wrangler what errors are logged?
Nno errors I can't get it anymore 
Jdo you have smart placement enabled?
Nyes
Jit's probably that. smart placement is pretty buggy with pages. i would recommend disabling it and then redeploying
Nokay, I enabled smart placement yesterday and got the errors yesterday and today
Nso it might be that
Jthat checks out
Twhere can i find deployment failure logs? i've run bun run deploy and it succesfully deploys but i look at the url it generated and it's nonexisting and in the CF dashboard it says deployment failed.
THello everyone: I have a question about the vercel output on next-on-pages:
- When I manually change the index.html file (I got this index.html after running “npx @cloudflare/next-on-pages” in the folder to generate the .vercel/output/static folder) in the .vercel/output/static: I mean manually change the text in the index.html from “TestingA” to “TestingB”
- Then deploy the static asset and _worker.js to the Pages use wrangler CLI.
- But when I visit the website, I still see the text “TestingA” in the home page, even I check the response on the network tab: it show text “TestingB” (as I expected) in the index.html
Can you explain why I observed this situation?
You can see clearly in the image below:
So I change the text from “Find in-depth information about Next.js features and API.” to “Thanh Le 95”. In the response of network tab, it shows correctly but when it rendered to the home page, it is still show the original one. Why is this happening?
T
TI have a Page that run on edge run time, fetch data from a Worker which talk to a SQL database. It seems like my pages is only return the cache version even I updated the data on SQL database, the Pages still return the old version. I think that is because of the caching rule of CDN, how do fix this issue?
Nyou need to tell nextjs to not cache the request
Nfetch(
https://...also you dont need a separate worker to access your db, if you use nextjs ssr you can access db from api routes and server components
Tinitially I tried this with nextjs. I have a Postresgql database and try to use the node-postgres or postgresqljs to fetch data directly but it seems both of them does not work on next-on-pages. the node-postgresql only works well on Workers. Do you have any idea how I can fetch data directly from ssr page or api route?
Nany compatible worker lib should be compatible with pages
Tthe issue for node-postgresql (pg) with next-on-pages here: https://github.com/cloudflare/next-on-pages/issues/605
GitHub
next-on-pages environment related information System: Platform: linux Arch: x64 Version: #202312122204 SMP PREEMPT_DYNAMIC Tue Dec 12 22:43:56 UTC 2023 CPU: (16) x64 AMD EPYC 7B13 Memory: 63 GB She...
Nhave you added node_compat = true to the flags of the worker ?
Nand also here
Tyes I add there.
Ncompatibility_flags = ["nodejs_compat"]
Nin wrangler.toml too
