Jonoroboto TL;DR: it’s faster, dev server go brrr, go upgrade

ADALIGO This looks like a solid iteration on Next.js Jonoroboto. The Fast Refresh change (module-level re-execution) is probably the most impactful here, aslo reducing unnecessary invalidation across the import graph has a real effect on dev feedback loops. Curious how consistent these gains are at scale and how this holds up on larger apps though?? especially with Turbopack already in place. But overall, seems like one of those low-risk, high-impact upgrades 🚀

BestCodes @jonoroboto I enjoyed reading that (hopefully I'm not a dummy 🫠)! Also your website is amazing! 😃

BestCodes Oh no! There's definitely something wrong with this cookie banner 🤣 Other than that, the website looks great, great job 🙂

BestCodes Why is the API key required? Does it only allow requests made using that API key?

BestCodes Oh no, is the website down? 🥲

MarnixB Awesome work! really hope you didnt need to find all pools by hand 😉 haha

Anshuman Bhardwaj Hi @agusnarestha, welcome to the Vercel Community! Thanks for sharing your project here. Could you update the post by adding more information about your experience and idea about the project?

DevGlyphX Convert the images at the DB to have them display properly or use Blob or host them and use the links (Probably better)

MarnixB Looks pretty nice! feels really personalised. Only thing i would maybe change is; The labels really scream AI WEBSITE. So maybe change that to something else 😉 but really nice work!

Edward J. Edge runs near the user, but your external API is usually in one region. Some requests will be “edge in far-away region → long round trip to API” and become flaky/slow. Occasional slow responses, TLS handshake delays, or throttling can look like random timeouts. Also when the upstream gets slow, you wait until something upstream/proxy aborts.

Edward J. especially when the work is “call an external API and wait” and that API latency is inconsistent. You can pin the function region to be near the external API (more stable than “near the user”). You get more mature reliability (Vercel’s own Edge Runtime docs explicitly recommend migrating to Node.js for improved reliability/performance).

Pauline P. Narvas I like it! Looks like the produce catalogue is empty, is that expected?

Jayarbrul The Backend has been deployed on Render. But I have used free version. So it take some time to load the page at first time. After few minutes, all categories are displayed.

Pauline P. Narvas Oh nice! Love it :D Definitely will be super useful

Sean Thank you @pawlean 😊

TheGravedigger Here is how a gravestone would look like!

Pauline P. Narvas Looks great! Thank you for sharing 😃

@amd Looks good

Hugo Lin Thanks for your loving!

Anshuman Bhardwaj Congratulations @krishna404 on getting selected for Vercel OSS Program. And kudos for building this tool. 🙌 What are your future plans for this project?

Anshuman Bhardwaj This is superb! Thanks for sharing the step by step guide here 🙌 Can't wait to try

Jonoroboto Tell us how you get on. One thing we haven’t figured out yet, that I would love to solve, is agent orchestration with git worktrees and how best to fire something off like that in one go. Think a less destructive Gastown, that you’d be comfortable throwing at a production repo. This is a simplified workflow, but should give you the idea.

Anshuman Bhardwaj Hi @tomaszowczarczyk, welcome to the Vercel Community! The analytics UI looks sick! Kudos for it. I see a dashboard tag in the list below the preview. Is this what you were hoping for?