I’ve had an app published for a couple months. Yesterday went into chat to make few changes and after publishing the updates the deployed version styling is completely different then Preview. I then went back to previous working version and re-deployed but still the differences persist and I can’t seem to get the deployed version back to the working state.
v0chat: superiormove1 - v0 by Vercel
deployed: Superior Relocation Services - Commercial Moving Experts
can you duplicate the chat from the “correct” version and redeploy?
duplicated chat and redeployed. issues persists - deployed version styling is not matching preview in chat
So there IS a version that exists that is “correct”? but…. its not in v0?
Could you somehow rerun it or dupicate from the Vercel project side of things? Or connect the Vercel project to github and then pull that correct version back into v0?
deployed version back in sync now after updating next.js and react to newer versions.
one question I had was while troubleshooting I downloaded the zip of the deployed and then compared to code in v0 chat. package.json were different even though I had just deployed latest version of what was in v0 chat, some dependencies were showing as ‘latest’ in downloaded code while in v0chat code same dependencies were pinned to specific version. Also, there were other small differences in deployed code like the presence of a /styles directory with a globals.css file inside but in v0 chat code that directory was not present. what’s expected behavior of how the code changes from v0 chat preview to deployed code? any documentation of what happens behind the scenes to the code upon deploy?
Ah this is absolutely GREAT to hear!
Hmmm regarding the rest of what you asked, that does seem rather odd.
I actually dont know about the “why” behind differing code. I dont think I have checked mine that “deep” before (but now I want to haha).
maybe @avik-creator or @hasriza may have some ideas.
And of course someone from the Team will surely read this soon and be able to give you a proper answer if there is documentation around it as well.
I will for sure be following up too.
Yeah sometimes the version in the deployed is of previous version. So before deploying it might be better to check it once
v0 supports projects without package.json files, without shadcn components, without layouts, etc and falls back to default versions. If you have some of these, it fills in the rest and sometimes does some merging to keep things functional. This looks like a git sync bug where it’s merging in the default package.json by mistake, which I’ve reported to the v0 team
Hey @gannhometech-1009, just checking in to see if you’ve found a solution for the differences between your deployed version and the code in v0 chat. If you still have questions or need further assistance, let me know!