v0 server errors and missing styles when importing from Figma to shadcn/ui plugin

It seems that something is broken in v0. When I was trying to open the generated code (using Figma to shadcn/ui plugin) it just showed a bunch of server errors which I tried to fix with v0 but the end result is that it’s just showing a pure HTML without any styles connected, the design mode is unavailable and the code panel is looking different and very weird like it’s sort of broken or something..

This error appears when opening a generated code using Figma to shadcn/ui plugin.

Server Error Error: Turbopack build failed with 1 errors: ./app Error: Next.js inferred your workspace root, but it may not be correct. We couldn’t find the Next.js package (next/package.json) from the project directory: /vercel/share/v0-next-shadcn/app To fix this, set turbopack.root in your Next.js config, or ensure the Next.js package is resolvable from this directory. Note: For security and performance reasons, files outside of the project directory will not be compiled. See https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#root-directory for more information.

at ignore-listed frames

Which Figma to Shadcn UI plugin do you mean? I don’t think we offer one officially, it may be a community project

@jacobparis I’m using this plugin Figma to shadcn/ui Plugin | shadcndesign
And everything was working fine until yesterday.

I also received this message from AI support chat about the error that I’m getting:

Thank you for sharing that error — this provides helpful context.

This is a v0 platform-level issue, not something you can fix on your end. The error indicates that v0’s internal build system (Turbopack) is having trouble resolving the Next.js package when processing code from the Figma to shadcn/ui plugin. The file path (/vercel1/share/v0-next-shadcn/app) is part of v0’s infrastructure.

What this means:

There appears to be a compatibility issue or bug with how v0 handles code imported from the Figma plugin. This is something the v0 engineering team would need to investigate and fix.

What you can do:

** Submit the support case — The form I prepared earlier is still available below. Include this Turbopack error in your submission so the support team has the full picture.*
** Use the Feedback option — In your v0 chat, use the Feedback button to report this error directly to the engineering team.*
** Check status — Keep an eye on v0-status.com for any related incidents.*

I’m sorry you’re running into this! The support team should be able to help escalate this to engineering for investigation.


And I tried to fix all errors with v0, and this how it looks, so the styles are completely missing

And my File Explorer Panel is now looking different, like something is broken or also missing styles..

That plugin is not official, you may need to reach out to the author for help Help & Contact | shadcndesign

My best guess is that it’s using a different version of Tailwind than you have installed. The tailwind.config.ts is from Tailwind 3. Try asking it to upgrade to Tailwind 4 and see if that fixes the styles

@jacobparis the plugin is using Tailwind 4.

And I still think that there is an issue on v0 side. Why does design mode stop working in all my new v0 chats, even without any Figma plugin usage.. and why does the File Explorer now is looking so weird?