#nextjs

Pauline P. Narvas Hey! I came across this thread and wanted to know how things were going 🙂 Could you check the following? Have you set NEXTAUTH_SECRET in your Vercel production environment? Is NEXTAUTH_URL set to your exact production domain (e.g., yourdomain.vercel.app)? Are GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET correctly added to your Vercel environment variables? Did you redeploy after updating your environment variables? In Google Cloud Console, is your Authorized JavaScript origin set to your production URL? Is your Authorized redirect URI exactly yourdomain.vercel.app/api/auth/callback/google? Does t

Pauline P. Narvas This is so fun! Thanks for sharing 🙂 Dataset Structure & Caching Static generation: Pre-process your dictionary at build time and store it as JSON in your public folder or import it directly Chunking: Split your dictionary by word length or first letter to reduce initial load Compression: Use gzip compression (Vercel handles this automatically) and consider storing data in more compact formats Search Performance Client-side filtering: Load the dataset once and filter in-memory using useMemo for React optimization Web Workers: For heavy filtering operations, offload to a Web Worker to keep the

Pauline P. Narvas Congrats on the growth! Keep an eye out for the next round of Open Source Program :)

Slugy Thanks for your response @pawlean 🫡

Pauline P. Narvas Great questions! Good luck getting contributions to this, I hope that folks in our community share some answers. Have you seen @eric-burel's work? He's done a lot of similar community work! We also did this session with him a couple of weeks back which may be helpful for your questionnaire and research. community.vercel.com/t/community-session-vercel-for-smes-and-open-source/9071

DRO Thanks for the tip Pauline! I will check it out. Note for others: submissions are closed as the deadline for delivery has been reached. I will mark this topic hopefully in such a way that this is clear.

Riz Hey @alok-q-kumar, I would recommend reviewing our Business Continuity/Disaster Recovery (BC/DR) Policy via our security portal (if you have any follow-up Qs, then, feel free to reach out to security@vercel.com, directly) 🫡

Jacob Paris Can you explain more about what errors you're running into?

Medhatbusinessacc 3223 while building the project the agent suddenly stopped (agent timed out) them after continuing the project there is no actual site, it keeps loading without any site on the screen, if i tried to open in new tap the whole page stop working, Agent assuming there no error in the code, I’ve downloaded the code and kept working on it, the main error is Failed to import, Glopals.css file failed to load due a syntax error in the code so it’s automatically blocked, and the whole project tree is not linked together properly, language toggle is not working properly(both languages in same pages), footer a

Peter Raedschde You are correct - this appears to be a malfunction in v0's ZIP import process. Based on the images you provided, I can see the factual discrepancy: Facts from the images: Import Dialog (second image): Shows proper lib/ subdirectory structure Contains files like lib/utils.ts, lib/errorHandler.ts, lib/neon-db.ts, etc. 855 files were selected for import Generated CodeProject: Files that should be in lib/ are placed at root level utils.ts, errorHandler.ts, neon-db.ts, etc. are missing the lib/ prefix Directory structure has been flattened Open Issues: Directory Structure Loss: The lib/ subdirector

Support Referredbyc having sme issue - exactl the same issue can someone from @vercel pls help. @pawlean

Jacob Paris The https: is a syntax error, an npm package will never have a : like that Is your code trying to import anything from a URL somewhere? That would be the most likely culprit for this

Petro S As I mentioned - the main issue that there is no such line in v0 code editor, but it automatically appears in the Github after pushing changes.

NathanK This is a common issue when font files are missing from the project. The error indicates that your app/layout.tsx file is trying to import local font files (GeistMonoVF.woff2 and GeistVF.woff2) that don't exist in your project's fonts directory. Here's how to fix this issue: project="font-fix" ... Alternative solutions: If you want to keep Geist fonts, you can install them via npm: npm install geist Then update your layout.tsx: import { GeistSans, GeistMono } from 'geist/font' If you have the font files, create a fonts directory in your app folder and add the missing .woff2 files there. Use sy

system Did you know there's another category dedicated to #v0 topics? A human should be here soon to help, but the answer may already be available even faster in one of these other posts. Our docs are a great place to start. vercel.com/docs/v0 We also have a walkthrough to help guide your workflow. community.vercel.com/t/become-a-v0-expert/5981 And these recordings can give you a look at v0 features and strategies in action shown by our Community: community.vercel.com/tags/c/events/42/v0

Wuzoobia Sorry, Vercel, we’re packing up. We’ve decided to move to a host that actually shows up when support is needed, and hey, we’ll save money while we’re at it. The backlog of unresolved issues in your community speaks volumes. It feels like your paid users are expected to crowdsource solutions while your team watches from the sidelines. If your business model depends on customers doing the heavy lifting, maybe it’s time to rethink who’s really earning that paycheck. Adios!

Yoshikage1kira Try to push your new version of code in a new branch of the repo you have connected to the deployment in vercel , after pushing the code in new branch . Visit your project in vercel and go to overview section at the bottom you would see active branches and there would be your new branch where you pushed your new code , click on three dots then View all Deployments , find your branch and click on three dots and then promote deployment after that you would figure out.