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 @parenthesesweb1-2378, welcome to the Vercel Community! Are you talking about v0 here or the Vercel platform? Can you share when was the last commit you pushed to the main branch? Is the person committing and pushing to GitHub part of your Vercel team?
Gil Seeing the same issue. Github has the latest commit (verified) and manually redeployed on Vercel but it doesn’t seem to pick up the latest version.
Gil fixed it! the problem was that my email for commits was different than my email for Vercel. Here’s how I fixed it: set the email for git for the project (this is from the project folder): git config user.email "your-vercel-email@example.com" then create an ‘empty’ commit because nothing has really changed: git commit --allow-empty -m "Force Vercel redeploy" and push it: git push origin main that did the trick