Install & CLI
`npx vectorvesper` runs an old version
npx caches packages, so it can run a stale copy. Pin the latest explicitly:
npx vectorvesper@latest add video-cardCheck what you're on with npx vectorvesper --version. Note that a local or global install will shadow the npm package, so if the version looks wrong, that's usually why.
`npm i -g vectorvesper` fails with EEXIST or EPERM
VV is npx-first, so you don't need a global install. These errors usually mean a previous global install left a locked executable shim behind (common on Windows when a terminal, editor, or antivirus holds the file). Just use npx vectorvesper … instead. If you really want the global command, close anything locking it, run npm rm -g vectorvesper, then reinstall.
"Component not found in the registry"
Check the slug against npx vectorvesper list. For example, it's physics-buttons (plural), not physics-button.
Peer dependencies weren't installed
You may have passed --no-install, or the auto-install didn't finish. Re-run the command the CLI printed, or add the component again without --no-install.
Config & detection
Components landed in `src/` instead of `src/components/vv`
Your import alias is set to @/ (or src/) rather than @/components/vv. The install location follows aliases.vv in vv.config.json: whatever you set there is both where files go and the import prefix. Edit it to @/components/vv, then remove and add the component to relocate it.
Tailwind shows "No" even though it's installed
Older CLI versions only looked for a tailwind.config.* file, so Tailwind v4 projects (which have no config file) reported "No". Update to the latest CLI. npx vectorvesper@latest info should now report Yes. See the Tailwind guide.
Rendering
"Hydration failed" / mismatch (Next.js)
A component rendered different markup on the server vs the client. Make sure WebGL components are imported with dynamic(..., { ssr: false }), and don't introduce non-deterministic values (e.g. Math.random()) during render.
WebGL component is blank, or "window is not defined"
The component was server-rendered. On Next.js, wrap it with dynamic(..., { ssr: false }). See the Next.js guide.
Styles are missing / the component looks unstyled
The component uses Tailwind and it isn't configured, or your content globs don't cover the install directory. See Tailwind setup.