Whenever I build, v0bot injects (and commits to git!) a dependency on “..”: “latest” in my package.json … which isn’t a valid dependency name and because it doesn’t exist in my lock file cause pnpm install to fail. When I change to pnpm install --no-lock-fileas is suggested, the build still fails because it attempts to copy itself (because of the injected “..” dependency) to it’s own subfolder … which obviously fails.
This is a fundamental problem with how v0 is “managing” hidden dependencies. I’m guessing you’re trying to inject a pre-loaded cache of dependencies? If so, you need to be more careful about v0bot not saving
Furthermore, v0bot keeps adding other “NextJS” related files into my repository even though my application is Vite-based. I really need to be able to trust v0bot to not inject useless crap into my repository that breaks my build.
Did you know there’s another category dedicated to v0 topics? A human should be here soon to help, but the answer may already be available even faster in one of these other posts.
Our docs are a great place to start.
We also have a walkthrough to help guide your workflow.
And these recordings can give you a look at v0 features and strategies in action shown by our Community:
At the moment, my build is working. I’m not 100% sure why, but I believe it is due to using the vercel-vite-plugin and the right combination of configuration options. I can’t say with 100% confidence that I understand the configuration, but at least I’m back in business.
