where 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.
Hello 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?
I 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?
initially 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?
this 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:
actually 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.
but 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.
@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
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?