DISABLE THIS! YOU MADE IT SO I CAN NOT VIEW OR BUILD ME WEBISTE! I NEED TO ENTER DESIGN MODE
Hi @uplift-7174, welcome to the Vercel Community!
I’m not sure if this is a bug. Where do you see this message? What happens when you click the X button on top right?
I have had this pop up too, but you should be able to just close it (x) and continue to work as normal. That is what I was able to do. And design Mode still worked exactly as it did before. Is there any more info or screenshots / video you can provide on what is not working here?
My words exactly! “production-grade work” for sure - can’t use design mode in the new preview, no embedded preview, no “fix for free” buttons, horrible output code with no verification if it actually works. This update broke everything and didn’t bring anything to the table.
look at what view button does:
THIS IS A BUG! You all just shipped this in the past day or two because it never showed this beta message before – your response is seems to lack the knowledge of this brand new feature that is a MAJOR update. Please escalate my issue to a Senior Software Engineer.
Inspect these two chats on the SAME EXACT project: https://v0.app/chat/anti-aging-page-Rm1BfchFjCp (this chat was used before the beta feature was launched, click the code and design buttons observe that it renders my website and WORKS)
Now I if I create a new chat in THE SAME EXACT project, it creates a new branch and shows the Beta label: https://v0.app/chat/nextovskindevelopment-netizen-v0-marks-test-NHueeDI6nWX And it does not work! It no longer renders the website.
The worst thing is that all new branches no longer work, all new chats no longer work, I have to use the chat that I used days ago before this MAJOR feature/beta was released.
Also, there should be an option to just turn it off:

Remove and revert this flawed feature from my account. You have made it
This popup modal belongs to the new beta feature it is just information panal, clicking X removes the modal – no big deal AND not the point of what I am raising.
The same exact project on a old existing branch chat shows this:
I just started experiencing the same thing. it show beta on top, site no longer renders in the environment, now there is a ‘preview’ link which opens the site in new window but not able to monitor the console now, I can no longer see what was changed in what file to keep track of changes. how do i disable this beta functionality, the new deployment/branch already caused 30+ hours of work
Hi @jerry-2306 and @uplift-7174, sorry to see this issue. Is the preview not opening for you? What happens when you click the Preview button on top right?
Could you share the chat URL after making it private so I can have a look and check with the team?
Also, does the code on GitHub look same as before? What happens when you open the code editor in your v0 environment: does the code look readable or is it gibberish as well?
https://v0.app/chat/nextovskindevelopment-netizen-next-ov-skin-1-9h7G8HoOB55 this is a brand new branch I just created right now it says preview not supported: ready, open a PR to create a preview deployment.
WorkingWorking…
Files
2b35c1e5-d6cb-4999-bc6f-bff57774789f.jpg1.7 MB3930d9df-79b1-4106-8c44-68d455d73d77-20-281-29.jpeg3.1 MB3e3c00dd-0803-4a94-91f2-9551e5197dc1.jpg3.2 MB3e3c00dd-0803-4a94-91f2.jpeg3.2 MB5c73253f-a622-4c5d-90d9-87fb412320ce.jpg1.7 MBDSC05651.jpeg1.1 MBIMG-3946.jpg2.6 MBNext-OV-Skin-Body-Sculpting.png2.1 MBThe Vault Stock -10983.jpg2.5 MBabstract-creamy-liquid-drops-on-surface.jpg2.9 MBanti-aging-flower.jpg2.9 MBanti-aging.jpg2.9 MBasian-profile.jpg362.8 KBasian-woman-clear-skin.jpeg1.7 MBasian-woman-water.jpeg1.1 MBbefore-after-results.png1.4 MBbefore-and-after/100.png577.3 KBbefore-and-after/11.png274.1 KBbefore-and-after/12.png312.0 KBbefore-and-after/14.png468.3 KBbefore-and-after/15.png789.4 KBbefore-and-after/17.png304.4 KBbefore-and-after/18.png479.7 KBbefore-and-after/2.png567.7 KBbefore-and-after/20.png652.8 KBbefore-and-after/21.png967.8 KBbefore-and-after/22.png821.8 KBbefore-and-after/27.png430.5 KBbefore-and-after/28.png634.6 KBbefore-and-after/3.png579.7 KBbefore-and-after/42.png467.4 KBbefore-and-after/43.png425.5 KBbefore-and-after/69.png350.8 KBbefore-and-after/70.png641.1 KBbefore-and-after/81.png330.0 KBbefore-and-after/82.png325.9 KBbefore-and-after/99.png656.3 KBbefore-and-after/BEFORE-AND-AFTER-1.jpg105.3 KBbefore-and-after/BEFORE-AND-AFTER-1.png1.4 MBbefore-and-after/BEFORE-AND-AFTER-12.png395.3 KBbefore-and-after/BEFORE-AND-AFTER-16.png1.6 MBbefore-and-after/BEFORE-AND-AFTER-17.png834.5 KBbefore-and-after/BEFORE-AND-AFTER-18.png1.9 MBbefore-and-after/BEFORE-AND-AFTER-19.png760.1 KBbefore-and-after/BEFORE-AND-AFTER-3.png1.3 MBbefore-and-after/BEFORE-AND-AFTER-6.png1.4 MBbefore-and-after/Body-Transformation.png1.1 MBbefore-and-after/Holistic-body-transformations.png1.0 MBbefore-and-after/Mom-Belly-Mend-1.png597.9 KBbefore-and-after/Mom-Belly-Mend-2.png812.6 KBbefore-and-after/Mom-Belly-Mend-3.png1.0 MBbefore-and-after/Mom-Belly-Mend-4.png872.5 KBbefore-and-after/Mom-Belly-Mend-7.png1.0 MBbefore-and-after/Mom-Belly-Mend-8.png626.8 KBbefore-and-after/Mom-Belly-Mend-9.png1003.2 KBbefore-and-after/Next-ov-Skin-Before-After-Images-1.png607.9 KBbefore-and-after/Non-Surgical-Tummy-Tuck.png707.4 KBbefore-and-after/before and afters /0 Bbefore-and-after/before and afters /100.png577.3 KBbefore-and-after/before and afters /11.png274.1 KBbefore-and-after/before and afters /12.png312.0 KBbefore-and-after/before and afters /14.png468.3 KBbefore-and-after/before and afters /15.png789.4 KBbefore-and-after/before and afters /17.png304.4 KBbefore-and-after/before and afters /18.png479.7 KBbefore-and-after/before and afters /2.png567.7 KBbefore-and-after/before and afters /21.png967.8 KBbefore-and-after/before and afters /22.png821.8 KBbefore-and-after/before and afters /27.png430.5 KBbefore-and-after/before and afters /28.png634.6 KBbefore-and-after/before and afters /3.png579.7 KBbefore-and-after/before and afters /42.png467.4 KBbefore-and-after/before and afters /43.png425.5 KBbefore-and-after/before and afters /69.png350.8 KBbefore-and-after/before and afters /70.png641.1 KBbefore-and-after/before and afters /81.png330.0 KBbefore-and-after/before and afters /82.png325.9 KBbefore-and-after/before and afters /99.png656.3 KBbefore-and-after/before-and-after-skincare.png712.7 KBbefore-and-after/bluecursive-1.png17.1 KBbefore-and-after/c-section-scar-healing.png305.6 KBbefore-and-after/footer-1.png3.6 MBbefore-and-after/footer-2.png1.2 MBbefore-and-after/footer-3.png2.8 MBbefore-and-after/footer-4.png2.9 MBbenefits-section.png139.3 KBblack-woman-flowers.png384.9 KBbody-sculpting-hero.webp29.3 KBbody-sculpting.webp17.2 KBbotox-edmonds-wa/NextOV-Skin-Logo.png17.0 KBbotox-edmonds-wa/bg.png1.0 MBbotox-edmonds-wa/bluecursive-1.png17.1 KBbotox-edmonds-wa/footer-6.png3.6 MBbotox-edmonds-wa/footer-7.png1.2 MBbotox-edmonds-wa/footer-8.png2.8 MBbotox-edmonds-wa/footer-9.png2.9 MBbotox-edmonds-wa/footer-logo.png62.2 KBbotox-edmonds-wa/hero-bg.jpg995.5 KBbotox-edmonds-wa/nav-logo.png17.1 KBbotox-edmonds-wa/novs-cursive-white.png15.6 KB
Select a file
Choose a file from the sidebar to preview
ConsoleTerminal
12:58:44.978Z**[SERVER]**
Initializing development environment for git-connected project...
12:58:45.632Z**[SERVER]**
Installing dependencies...
12:58:46.610Z**[SERVER]**
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: vaul@0.9.9
npm error Found: react@19.1.0
npm error node_modules/react
npm error react@"19.1.0" from the root project
npm error peer react@">=16.8.0" from @floating-ui/react-dom@2.1.6
npm error node_modules/@floating-ui/react-dom
npm error @floating-ui/react-dom@"^2.0.0" from @radix-ui/react-popper@1.2.1
npm error node_modules/@radix-ui/react-popper
npm error @radix-ui/react-popper@"1.2.1" from @radix-ui/react-hover-card@1.1.4
npm error node_modules/@radix-ui/react-hover-card
npm error @radix-ui/react-hover-card@"1.1.4" from the root project
npm error 4 more (@radix-ui/react-menu, @radix-ui/react-popover, ...)
npm error 72 more (@radix-ui/react-accordion, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8 || ^17.0 || ^18.0" from vaul@0.9.9
npm error node_modules/vaul
npm error vaul@"^0.9.9" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error peer react@"^16.8 || ^17.0 || ^18.0" from vaul@0.9.9
npm error node_modules/vaul
npm error vaul@"^0.9.9" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/vercel-sandbox/.npm/_logs/2026-02-03T20_58_45_731Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/vercel-sandbox/.npm/_logs/2026-02-03T20_58_45_731Z-debug-0.log
here is the same exact project on an existing branch that was created before you all rolled out this BROKEN beta feature:
THE PREVIEW WORKS!
one week ago before beta was rolled out all new branches DID NOT SAY BETA AND EVERY NEW BRANCH THE PREVIEW WORKED!
Is it possible that your old branche/preview was running on react 18 and now because you are starting a “fresh” project it forces you into react 19? so you get de depencie errors and so does the preview not show anything. in the new duplicated chat can you ask to maybe downgrade to react 18 and make sure all depencies are the right version for this react version? then see what happens. Sometimes versions gets stuck or get auto upgraded when pulling and pushing/duplicating stuff. If that doesnt work you can maybe start asking the chat to remove/replace vaul
Let us know ![]()
IF THAT IS THE PROBLEM! THAT IS A HORRIBLE PROBLEM TO HAVE!
So when you start a chat with the new beta, WHICH YOU CANNOT OPT OUT OF, you are FORCED to update MAJOR libraries? Oh and by the way, the old chats DO NOT FORCE you to update, they use DIFFERENT libraries.
Yeah that is a reasonable developer and user experience.
![]()
![]()
![]()
Totally agree the system is horrible - we need the old system ASAp im going to lose customers
Hello, everyone!
Design Mode will be coming back at some point but right now it is being improved and worked on.
Appreciate your patience!




