I am also having the same issues as “” Codebase Destruction"“, “” Random Data Loss”" and “” False Implementation"“”
Add to that the fact the own v0 model uses old version of several packages, NextJS included, where it should be only using the very latest version (if you start a project now, it will be used v15.2.4 while the latest version is v15.3.3), also does not implement Turbopack itself, uses Tailwind v3.4.17 and much more. Once they start a new project to an user, it could at least, bootstrap it using their own npx command with all flags enabled. Is this really hard to implement?
I spent, at least, $10 dollars or more, ONLY, literally only to restore things that was or deleted or broke or something (if there is a way to get this back, I’d love to know and apply).
Also, breaks import files everywhere and then, I need to spend more and more only to fix the issues the own v0 created. I get several times messages like "“looks like the import of components/abc.tsx is broken”, and again, this is critical when spending money on something is happening.
Things I think would be amazing to be implemented in a near future
- Use Context7 to get ONLY the latest packages versions to be used along with their documentation. Stop implementing code for old package versions
- Whenever i push the v0 code to a Github repo and clone it in my computer and make any modification and push it into the Github repo again, DO NOT REVERT to the previous version. Yesterday I spent some time to update all Shadcn and Tailwind implementations and code, pushed into the repository and what happened? v0 just to revert to the previous version and that is it. All the updated code was wasted. Looks like this is only a one way hand. Let me add some code and make v0 understand this new code. Or even better, make a VSCode extension and make this work inside VSCode or create a vscode fork, I don’t know which way v0 will choose, but this would be MUCH better than having this web based development feature. You know why? Simple
As simple as that. Whenever I need to write some command, just to show up one single letter, takes 5 to 10 seconds to appear. Yeah… that long. And my machine is “old” but still good (MBP M1 16gb). So, a vscode fork or extension will be MUCH better than cloud based
- And here i will say what I personally thing would be amazing to have in v0.
Imagine that on the left of this box here
You can have a switch called “dev mode” or something like that (because figma stole this naming convention, right?) and this will enable a checkbox on the top left (or right, you decide) of EACH element in the page. Each checkbox checked will represent an element that CANNOT be deleted by any means. It would represent that it can be improved, changed position and everything else but be deleted. Why that? Simple, so v0 will never need to think about that element to delete and destroy the whole codebase anymore. Yes, if any of you want to take sometime and search among my feedbacks and iterations I had yesterday, you will see that was basically asking v0 to restore something that was working before, then I asked to do something and something completely unrelated to the question was deleted and I had to ask v0 to restore it and reach to the point it was before (yes, quite annoying). So, this checkbox would prevent such thing and only improve v0.
- This one here is personal but I’d love to have this implemented so I wouldn’t need to do this manually.
Create a
changelogfolder, where each iteration would be a markdown file. Like you can see in the image above, I’m currently in the v214 of this project
right?
((which shouldn't because v0 likes to destroy everything it creates...So I could see the steps, the code itself, the scripts created and everything else. It may looks silly to you, but it is something I’d love to have.
EDIT 1
Another issue I had was to implement this DAL pattern into the project. The v0 answer when I asked to refactor using this pattern was literally
The own v0 can’t read NextJS docs? I mean, I get it might be not the best option to search web and stuff but make at least the own NextJS docs available inside v0… No?
Well… I may have many other things to add, but I think these ones are the most urgent in my opinion.