okay, I enabled smart placement yesterday and got the errors yesterday and today
okay, 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://..., { cache: 'no-store' })Nalso 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
Tthis is my setup: I have a nextjs page and I use the edge runtime with pg to fetch data from database and then deploy it to Cloudflare through Git intergration. this is the error I got when Cloudflare try to build the project through the dashboard:
T
T
Tthe second image is from Prisma docs, they also mention pg currently not work on next-on-pages
Nsad
Nuse D1 
Thow do I do that in next-on-pages?
Nseem like the lib isnt compatible so dont need to test
Nyou can use D1 as a DB if you want SQL database
Tactually I use AWS Lambda for fetching data cause I test the the backend with aws lambda and worker and found that server is close to database is better then server is close to user when you fetch database. the response time of aws lambda is two times faster than workers when fetching data from the database.
Nhave you enabled smart placement ?
Ti try but it said that my worker does not make enough subrequest.
HYou should only be using node_compat or nodejs_compat, not both
Tyes. next-on-pages use nodejs compact and pg use node compact. so maybe they dont like each other
NI only use nodejs_compat
Dyes nodejs_compat and node_compat are indeed incompatible 
(there's some work being made to make them compatible soon-ish)
(there's some work being made to make them compatible soon-ish)
HOh, I thought it was to remove the need for node_compat at all?
HSo that everything would be under nodejs_compat
Tbut I think the issue pg doesnot work with next-on-pages is because of the build time with webpack. I use the pg lib for Workers and it works really good.
D@Hello, I’m Allie! yeah I thought that too, but my current understanding is that we don't really want to put everything under nodejs_compat as that would introduce those modules/polyfills in the runtime, forcing us to basically support them forever and handle their updates/deprecation accordingly... so a bit of a burden 
So the solution is, I believe, to put under nodejs_compat as much as it makes sense but still have node_compat for the less stable polyfills, and make nodejs_compat and node_compat compabile
So the solution is, I believe, to put under nodejs_compat as much as it makes sense but still have node_compat for the less stable polyfills, and make nodejs_compat and node_compat compabile
Nwhy not separating nodejs_compat in multiples flags
Nso you only add what functions you use
Nlike ["nodejs_asset", "nodejs_Crypto", etc]
Npg lib should use node:module but its not in the screen you sent
N
Nmaybe you can configure webpack to change these imports
HThat would just make it more confusing for people using a framework, if said framework needs ten different modules
Nor some static analysis on your code that guess what you are using (gonna be nightmare)
HIsn't that what
nodejs_compat is already? Under the hood, they may not be exactly what Node does, but if the input/output are the same, then aren't those modules/polyfills already being supported perpetually?DI guess that would be possible, but what would be the benefit of it? 
Nperformance, idk if there is some performance gain if we dont use nodejs_compat but probably
HNot really. All of
nodejs_compat is already built into the runtime, so the flag only determines whether you actually have access to it or not.HYou could make an argument for having the flags as a way to pressure a framework to use less of them(making them more compliant with cross-platform standards), but not sure whether that would actually work
