Vite SPA v0bot forcing NextJS dependencies in package.json

I have a Vite SPA application using the vercel-vite-plugin … and when I ask/tell v0 to remove all dependencies on NextJS from package.json, it says it does so, but four unwanted/uneeded dependencies remain:

"module": "1.2.5",
"next-themes": "0.4.6",
"path": "0.12.7",
"next": "15.5.3"

If these are runtime dependencies needed by vercel … I can understand their need to be included, but I would expect them to be injected by the vercel build/deploy system not to be injected by v0bot and stored in my git repo.

These do not seem to cause any harm that I can tell at the moment, but it is also disconcerning (trust-reducing) behavior by v0bot to 1.) say it is removing the dependencies and then 2.) keep the dependencies in.

Hey @travisahoffman-2371 I think they aren’t runtime requirements of vite . I think v0 might be hallucinating dependency requirements. Maybe, try adding a pre-commit hook or CI check that fails if those packages reappear ? However, Vercel constantly is improving V0 so I am pretty hopeful about this!

1 Like

+1!

Thanks for the feedback, this has also been shared directly to the v0 team.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.