⌘K
Abhivarde show some love on X 🖤 https://x.com/varde_abhi/status/2092246715747455308
Abhivarde shipped an update to gitphere, a globe that maps a GitHub user's following list by location. ↳ now installs as a shadcn component ↳ drop it straight into any Next.js project ↳ your own GitHub token, your own server, no dependency on mine https://x.com/varde_abhi/status/2093577937975136414
Suheb This looks like a useful approach, especially keeping the QR generation fully client-side. Using Next.js 16 should also make it easier to keep the toolkit fast and lightweight. The focus on privacy is a nice touch since users don't need to upload their QR data to a server.
Kris Dev Thanks! That was exactly the goal. I wanted the core QR workflow to stay fully client-side so users can generate, style, and export their QR codes without sending the payload to a backend. It also keeps the architecture simple and lightweight, which fits well with the kind of utility I want QR Forge to be. Appreciate the feedback!
Anshuman Bhardwaj Hi @nisarganand541-8212, welcome to the Vercel Community! I'm so happy to see your enthusiasm here. I'd suggest starting small and building v0 projects with them in hackathons or college competitions. Once you have a solid foundation of organizing and managing small events, you can also use our https://meetup-sdk.vercel.com/ to organize a meet up and we'll support you there. Let me know if you have any specific questions.
mr.li512486 Hi Saqib and Vercel Community Team! I’m also a college student, from Guangdong, China, and I’m currently organizing a student-led AI developer club at my college. We are starting with around 20 core members, focusing on AI development, Vibe Coding, Next.js, Vercel, v0, AI SDK, Codex, and other modern AI development tools. After seeing your experience building a Vercel community at your university, I realized that this is very close to what we are hoping to build on our campus. We would love to explore whether there is any way for us to work with the Vercel Community as we start organizing workshops, student projects, and eventually campus developer events. If anyone from the Vercel Community team has advice on how we should get started, I would really appreciate it! Thank you!
sara keyser @nisarganand541-8212 This is an awesome mission! I'd also reach out to your college's student activities/student engagement team and any campus communications or student organizations office. Maybe they can help promote your events through the campus events calendar, newsletters, social channels, and student org network. You could also partner with some other student groups to get the word out and co-host the first workshop. I would also explore the local library, coffee shops or places where you can get on local event calendars so you can attract people outside the school..even your city's chamber of commerce. Lastly if there are any engineer teams based in your area - directly connecting with them to host a talk, or join your events, and who knows - this may also lead to internships and opportunities for you and your community! Best of luck 💫
Abdurhaman Nur The test version of the website on Vercel is called a **Preview Deployment**. It is used to test new features, design changes, and updates before making them available to everyone. It usually has a separate Vercel URL and does not affect the live website. The live version is called the **Production Deployment**. This is the version that users access through the main website domain. It contains the approved and final changes that are ready for public use. In simple terms, the test version is for checking and reviewing changes, while the live version is the official website that visitors use.
Suheb Thanks for the clear explanation. This makes the difference between Preview and Production Deployments on Vercel much easier to understand. Using Preview Deployments for testing before pushing approved changes to Production seems like a good way to reduce the risk of issues on the live website.
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.
Chintan Based on the detailed debugging steps you've shared, your conclusion is spot on: this is almost certainly a platform-level edge routing or provisioning issue rather than an application-level bug. The presence of the x-vercel-error: NOT_FOUND header on both the custom domain and the direct .vercel.app URL—especially when bypassing Deployment Protection—confirms that Vercel's edge network is failing to map the URL to your specific deployment ID, despite the build succeeding and showing as "Ready". While waiting for a Vercel team member to manually re-sync or check your edge routing on their end, here are the most effective steps to force a resolution or rule out the remaining edge cases: 1. Trigger a Redeploy Without Cache (Clean Build) 1. Double-Check the Root and Output Directory 1. Check for Account-Level Restrictions For more context on how Vercel categorizes these errors, you can refer to their official documentation on the DEPLOYMENT_NOT_FOUND error - https://vercel.com/docs/errors/deployment_not_found.
Amy Egan It looks like you got it working. Both URLs seem to go to the same site at the moment. Do you still need help with this?
Eldargvideo 8087 Vercel’s managed apex ALIAS is serving a stale flatten. Your proof that hitting `216.198.79.1` / `64.29.17.1` serves the right deploy is the diagnosis. Put explicit A records to those two IPs at the registrar (keep MX/TXT), or move DNS off Vercel nameservers and CNAME www + ALIAS apex to `cname.vercel-dns.com`.
