Skip to content
VenusUI
Get started
Docs

Troubleshooting

Fixes for the errors people run into most often.

Common problems

Unknown registry "@venusui"
Your shadcn CLI couldn’t find the namespace in the shadcn registry index. Use the latest CLI (npx shadcn@latest), install by URL, or register it with its address: npx shadcn@latest registry add @venusui=https://venusui.com/r/{name}.json.
No components.json found
The project isn’t set up for shadcn. Run npx shadcn@latest init first.
Module not found: Can't resolve 'motion/react' (or another package)
The CLI installs npm packages for you. After a manual install, run the npm install command shown in the component’s Manual tab.
An animation doesn’t run
Animated components add keyframes and theme variables (e.g. --animate-marquee) to your global CSS. After a manual install, copy the CSS from the Manual tab. Also check your operating system’s reduced-motion setting: components stay still when it is on.
Colors look wrong or classes such as bg-card do nothing
Your CSS is missing the shadcn theme variables. Run npx shadcn@latest init, or add the variables yourself.
TypeScript errors about ref props
VenusUI targets React 19, where ref is a regular prop. Upgrade React to 19.
Tailwind classes from a component have no effect
VenusUI targets Tailwind CSS v4. See Install Tailwind CSS for upgrading from v3.
3D components show an empty area
3D components render with WebGL. Check that WebGL is enabled in the browser; on very old devices it may be unavailable.