#react

Ahmad Sajid This is a really fun twist on the usual snake concept. Making the player the one being chased gives it a nice sense of pressure right away. The 5-second spawn interval feels like a good starting point, but I could see the difficulty becoming much more interesting if the interval gradually decreases as the score increases. I also like the Top X% idea, especially with the global leaderboard. It gives the short runs a bit more purpose and makes you want to immediately try one more time. The React/Canvas \+ Supabase setup is a nice combination for a small browser game too. I’d definitely be interested in seeing things like different virus behaviours or temporary power-ups added later.

Physikz2 Thank you for the feedback Ahmad I really appreciate it and yes i agree with some of your points as Ive considered them myself. If the global counter does get higher maybe I will introduce new things here and there

Olivia Carter Really nice approach, especially the way you’re treating locales as part of the content structure rather than duplicating pages. The ancestor-chain resolution for nested service pages is an interesting detail too. I’m curious how you handle adding a new locale later — does the existing content structure make that fairly straightforward, or are there still parts of the routing and structured data that need manual work?

Jacob Paris This looks great, I like that you copied the shadcn theming shape so it feels more familiar. Your included themes do look more like recolors though, it would be cool to have more variety like tweakcn.com

Aniket Pawar Thanks Jacob, theme builder is underway and will be released soon.

Amy Egan That is so much fun! Thanks for sharing it

BestCodes I love this @damilareoo :) I'm curious - why did you name it that?

Damilare Haha!! Thank youuu. It's just a nick name my friends call me lol

Rahmankazemi87 4375 اینا متعلق به کنه ایا

Belty6979 5979 Really impressive how much you’ve packed into the calculator layer, especially keeping the calculations client-side while still maintaining a consistent UI across so many tools. I’ve been working on a simpler age-calculation tool as well, and one thing I’ve found interesting is how much the experience improves when the result shows the exact breakdown rather than just a single number. Projects like this make it clear that calculators can be useful standalone tools, not just small features inside a larger app. For anyone interested in seeing a more focused example of that approach: https://myagecalculate.com/

BestCodes Super excited to try Next.js 16.3 soon Added to my reading list!

Krogharro 7879 hey this is really cool! Loving the work

Abhivarde nice stack choice!

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Ryu Hi Zetnick258, This sounds more like the v0 sandbox/file-sync layer getting stuck than a Next.js or React code issue, especially since it tends to happen around builds, large edit batches, or repeated tool calls. A few things I’d try to narrow it down: ``` 1. Avoid sending “continue” while it is retrying sandbox health checks. 2. Refresh once and wait for the preview/editor to reconnect before giving another prompt. 3. Run only one active v0 chat against the same project at a time, since shared projects can involve the same app/files. 4. Split the workflow into “edit files first” and “run build/typecheck after” instead of asking for both in one long multi-step prompt. ``` A useful prompt pattern might be: ``` Make the requested code edits only. Do not run build, lint, or typecheck yet. After all file edits are complete, stop and summarize the changed files. I will ask for the build step separately. ``` If it still happens, I’d capture one concrete example with the chat URL, approximate timestamp, the exact prompt that triggered it, and the last visible tool/action before `files-sync` locked. I would avoid posting private project links or secrets publicly, but that small reproducible sequence is probably the most useful signal for someone from Vercel/v0 to investigate.

Jacob Paris Your headers are being added twice. When this happens they get merged together and that's probably creating an invalid final value. I'm guessing you've tried to configure the same CORS setup in both Laravel and in Nginx/OpenResty. Removing one of these should fix it When you check your request in the network tab of your browser, you want to see these headers and no duplicates ``` Access-Control-Allow-Origin: https://elkj-pos.vercel.app Access-Control-Allow-Credentials: true ``` Alternatively: the easiest way to get around CORS is to not make any cross-origin requests in the first place. - If you're using a full stack framework like Next.js, you can route your requests through the same-origin Next.js backend toward your API. This might feel like an extra step, but server -> server requests are much faster than client -> server as they're between (or within) datacenters. - You could also use proxy rewrites to route traffic from your app domain to your Laravel Server. We use this to mix Next.js pages into the Discourse platform on this website. https://vercel.com/blog/how-we-run-vercels-cdn-in-front-of-discourse#vercel-as-a-cdn Both of those solutions mean your website is only ever sending requests to its own domain, which eliminates CORS and allows you to use more secure authentication methods like HttpOnly SameSite cookies.

Amy Egan I love seeing so many awesome things people have build with shadcn/ui! Thanks for sharing this dashboard toolkit

Vaibhav Gupta Glad to see you liked it!!

system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Ryu Hi Solomon, The `Functions` tab only showing `/api/auth/[...nextauth]` is not necessarily a problem by itself. Static App Router pages will not always show up there as functions. The more important signal is the exact 404 type and which URL is returning it. I’d separate three cases: ``` 1. Unique deployment URL returns 404 2. Project/production alias returns 404 3. Only specific app paths like /todo return 404 ``` Can you test the unique deployment URL from the deployment details page, not just the project alias? ``` curl -I https://<deployment-id-or-unique-url>.vercel.app/ curl -I https://<deployment-id-or-unique-url>.vercel.app/todo curl -I https://study-hub-phi-sand.vercel.app/ curl -I https://study-hub-phi-sand.vercel.app/todo vercel inspect <deployment-url> ``` If the unique deployment URL works but `study-hub-phi-sand.vercel.app` returns `DEPLOYMENT_NOT_FOUND`, that points to an alias/routing association issue. If the unique deployment URL also returns Vercel’s platform `DEPLOYMENT_NOT_FOUND`, then that is much stronger evidence that the deployment is not being served at the edge even though the dashboard says Ready. The most useful escalation details would be: ``` deployment URL tested: production alias tested: deployment ID: exact UTC timestamp: x-vercel-id from the 404 page: vercel inspect status/target/aliases: ``` I’d avoid redeploying repeatedly for now unless you need to restore service, because the current broken deployment state may be what Vercel needs to inspect.

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. https://vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

Ryu Hi Hero, I’d first separate “Safari is slow to get the document” from “Safari gets the document quickly but renders a blank page for a while.” A quick way to check is to run this in Safari’s console after a slow load, then compare it with Chrome on the same iPhone: ``` const n = performance.getEntriesByType("navigation")[0]; console.table({ dns: Math.round(n.domainLookupEnd - n.domainLookupStart), connect: Math.round(n.connectEnd - n.connectStart), tls: Math.round(n.requestStart - n.secureConnectionStart), ttfb: Math.round(n.responseStart - n.requestStart), download: Math.round(n.responseEnd - n.responseStart), dom: Math.round(n.domContentLoadedEventEnd - n.responseEnd), total: Math.round(n.loadEventEnd - n.startTime), }); ``` If `dns`, `connect`, `tls`, or `ttfb` is much higher only in Safari, I’d test Safari with iCloud Private Relay/content blockers disabled, and compare Wi-Fi vs mobile data. I’d also compare the custom domain against the `*.vercel.app` URL. If the Vercel URL is fast but the custom domain is slow, then I’d look at DNS, SSL, or anything proxying the domain. If the network numbers look normal but the screen stays blank, then I’d focus on client rendering: large JS, blocking third-party scripts, fonts, CSS, hydration, or an app shell that does not render meaningful HTML before client code runs. One useful isolation test is adding a very small static page, for example `/plain`, that only returns simple text and no heavy components. If Safari loads `/plain` instantly but the homepage is slow, the issue is probably in the page code/assets. If `/plain` is also slow, the issue is more likely network/domain/browser-path related. The most useful detail to share next would be the timing table from Safari and Chrome for the exact same URL.