last comment
⌘K
BestCodes Must say, my portfolio looks pretty sick 😏 However, I do notice that some of the images are broken or not loading. Any idea why that's happening? Great job @skb3611 😃
Skb3611 You need to provide the images for your projects (the best ones that you use for marketing) or else im thinking of adding the github repo banner as default , what do you think?
BestCodes NO. I refuse to be jealous of your website's traffic numbers 😤 Just kidding, that's a super cool idea 😃 I might have to try this. Do you have any plans to open-source it?
Neeeophytee Thanks! Yeah it's been fun to dig into. Here's the dashboard with realtime data from my own site if you want to poke around: botwatcher.vercel.app/demo Not open-source yet but it's something I'm seriously thinking about for the core detection layer. Right now the bot signature list is the part that needs the most community input since new bots show up constantly. Saw that you built Discraft and that it deploys to Vercel. If you want to see what's hitting bestcodes.dev I can get you set up in a few minutes. Just the log drain, one CLI command and you'd have a live dashboard. Happy to host it fo
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! 😃
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)
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).
