⌘K
Jacob Paris v0 has supported Tailwind 4 by default for about two weeks now, you can test this by creating any new chat and downloading the zip to see the package.json
Dilshod Hey @jacobparis, we’ve been having no luck trying to get our starter kits run on v0. It just doesn’t work at all, there seems to be some SSR related issue specific to v0 which appear as soon as we start adding config files like layout.tsx. We’d really appreciate any help or guidance to have a working project with Tailwind v4 and custom config files like layout.tsx, globals.css, etc. This is currently blocking 1000+ components from being available to open in v0 (we currently only offer opening in Bolt.new). This is our starter kit: github.com/untitleduico/untitledui-nextjs-starter-kit
Dilshod I went ahead and created a simple v0 chat using our Next.js stater kit and as you can see we get some SSR related errors which are impossible to debug. v0.dev/chat/simple-react-app-iCLVmzk9kTo
Jacob Paris Are you seeing any network errors or getting any other behavior when the stream ends? This looks like it was interrupted prematurely
Radin I uploaded the request and response images As you can see, the request appears to be complete and the stream is not interrupted, but in the code changes section, no code is loaded. What is the cause of the problem?
lukek Are there any integrations that need to be added that were with the original version? Did you recently delete the original version? Does it not happen for the original version and only when it’s uploaded from its Zip file? Have you tried clicking Fix with v0 to see if the problem is an easy fix?
Jahidhasa007 Hi there, I'm experiencing an issue with uploading zip files. I've successfully uploaded the original version of my project before, and it was working perfectly. However, now I'm unable to upload the same zip file, and this issue isn't limited to just that one file; it seems to affect all zip file uploads, showing a "never file problem" error. Could you please help me understand what might be causing this and how to resolve it? Thanks, Jahid
lukek I’m not sure man but maybe a dev can help you out, try find something else to do in the mean time.
Jacob Paris This appears to be caused by the redirect removing the trailing slash after system/?, I've flagged to the team to investigate Do you have a trailing slash at the end of your import like this? If so that's probably the culprit and should be able to fix by removing it import { SomeSystemIcon } from '@wix/wix-ui-icons-common/system/'; npmjs.com/package/@wix/wix-ui-icons-common Otherwise this is likely on our end and will have to wait for the fix, in the meantime you might have success switching to their old package or using a different icon library temporarily npmjs.com/package/wix-ui-icons-commo
Nitayrabi Thanks for the quick reply @jacobparis! I'll have a look at our code to see if there's trailing slash imports.
Jacob Paris We have recently updated v0 to use Tailwind 4 by default for new chats – this should not have broken the existing chats though. If you're only seeing this in new chats in the existing project, then that might be a gap on our end, maybe we need to prevent it from upgrading on forks or something like that If you ask v0 to set it to tailwind 3 in the package.json that should restore your original functionality
trc Thanks Jacob, instructing v0 to set tailwind to v3 in the package.json fixed the issue, my project is now working properly again. Massive thanks!
Simon I tend to agree. The number of issues now being generated for even minor updates seems to have increased substantially. In particular I am seeing complete rewrites of page code for simple updates (which either completely change the page UI/features or break them) and I am seeing a LOT of issues with simple updates breaking things like importing components that were already working and weren't part of the requested change. I never expect perfection and am comfortable that with AI code there will be errors and issues, but when it happens as much as it now is you start to look elsewhere. Which is
Pauline P. Narvas Hey Dean! We hear and appreciate your feedback. I'll get this shared with the v0 team as we continue to make the product better. Could you share any chat examples or screenshots before and after? It'd help a lot!
dan Shame, i'm 2 weeks into using v0 and I've gone from 'wow' to 'wtf' quite quickly. Costly, creates more bugs than features, and insanely expensive. I accidentally used the large model, which has to be some sort of scam in my view, bordering on gambling. As you have no idea what the outcome will be or the cost, you're essentially praying the large model will solve the problem - which it then doesn't, costing you 1/4 of a premium chatgpt monthly subscription. This is just...idk. so much potential wasted here it seems.
