Hey Guys, I am stuck on this issue while using next-on-pages next-dev module, not able to get local
Hey 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)
17 Replies
Is it possible to get a flag like wrangler dev's
--remote on the next.js dev server? Doing any sort of integration testing with R2 bindings, for example, is really hard at the moment.Afraid not, the bindings in next dev are emulated using miniflare, so it's local only
Trick 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?
Hi 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.
i try to use node-postgresql library in next-on-pages
Hi, I randomly get 500 Internal Server Error when going to my ssr streaming nextjs website, I dont find any other error
sometimes I get the error 3 times in 1 minute and then I can't get it once in hours
If you tail your deployment with wrangler what errors are logged?
no errors I can't get it anymore 🥲
do you have smart placement enabled?
yes
it's probably that. smart placement is pretty buggy with pages. i would recommend disabling it and then redeploying
okay, I enabled smart placement yesterday and got the errors yesterday and today
so it might be that
that checks out
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?
