Demo, all content is generated
Question

How do I get my v0 project into my own GitHub repo and keep working locally?

Open · 643 views · asked by haru_m · edited

Built most of my portfolio in v0. Now I want it in my own GitHub so I can edit with Cursor and deploy on Vercel with my domain. I see Download ZIP, a GitHub thing and a deploy button. Which one, and can I still go back to v0 after?

What I’ve tried

Downloaded the ZIP, ran npm install, got peer dependency warnings about react 19 and stopped there.

Comment
following, same situation with my portfolio rosa_m · edited

3 answers

rafa_dev · edited

Use the GitHub connection in v0 rather than the ZIP. It creates a repo and pushes the code, and later v0 changes land as commits (on a branch you can merge). The ZIP is a one-time copy, no way back.

Locally:

git clone <repo>
cd <repo>
npm install --legacy-peer-deps   # only if the react 19 peer warnings turn into errors
npm run dev

Peer warnings with React 19 are common and usually harmless; only use --legacy-peer-deps when install actually fails.

Then import the repo in Vercel and add your domain there.

Comment
Did the GitHub route. When I edit in Cursor and push, does v0 see it? haru_m · edited
It picks up what's on the connected branch, but I'd not bounce back and forth daily. Pick one place as the source of truth, or you'll be resolving conflicts a lot. rafa_dev · edited
yuki_builds · edited

I went back and forth between v0 and Cursor for a month. My advice: use v0 for new sections/components, pull them in with the shadcn add command, and do all the rest locally. Much less confusion than syncing the whole project.

Comment
mei_lin · edited

About the React 19 peer warnings: most come from libraries that haven't widened their peerDependencies range yet. They usually work fine. Check the library's changelog if something actually breaks.

Comment