FAQ & troubleshooting

No. There is no runtime dependency on us. Each item is a native Web Component — you copy one self-contained vs-*.js file into your project, register it once, and it becomes your code.

Yes, in as many projects as you like, including client work. You may not resell the catalog itself as a component library or template pack. The license walks through real yes-and-no cases.

No — and that is the point. Nothing we ship can break your app. If you want a newer version of something, copy it again.

Yes — anywhere, server rendering included. The catalog ships native Web Components (custom elements), and every file is safe to import on the server, so Next.js, Nuxt, Astro and SvelteKit render the page with no ssr: false or client-only wrapper. See React, Next.js & other frameworks.

Yes. Every item is a standard custom element — the same vs-*.js file works in React, Svelte, Vue, Angular, Solid or vanilla. For React and Next.js the code panel also gives you a typed wrapper (VsX.tsx) and TypeScript types (vs-x.d.ts): props, arrays and on… events work like any React component, on React 18 and 19. See Frameworks.

By default it reads your design tokens (var(--…)) and falls back to built-in literals when they are absent — so it renders either way, just un-themed. Define the matching CSS custom properties on :root (or any ancestor) to bind it to your palette and control scale. See Theming.

Nothing external is needed — every effect ships inlined inside the component's own file. If motion is dead everywhere, reduced motion is on (see below).

A component is one self-contained file. Some items reuse another tag via a sibling import './vs-button.js'; when you copy from the site or pull over MCP, those siblings come in the same bundle. Keep them next to each other, or fix the one relative import line.

Give the host element a size. Background animations are absolutely positioned inside a relative parent — with no height on that parent, the canvas is 0px tall. Also check the browser console: WebGL items report a lost or unavailable context there.

Reduced motion is on — either the OS setting, or data-motion="static" on <html>. That is by design; each animation renders a single static frame instead of looping.

Restart the editor, not just the chat panel. MCP servers are loaded at startup in every client. If it still fails, open the client's MCP log — a 401 there is an auth problem, a network error is a proxy or firewall.

The key is missing, does not start with vsx_, was revoked, or the account is not PRO. Check the header is exactly Authorization: Bearer vsx_….

The auth backend blipped. Retry in a few seconds; nothing is wrong with your key.

Plan changes take up to a minute to reach the MCP server. Wait, then retry.

Technically yes, but the key identifies one account and the licence is granted to one developer. Give everyone their own — it is also the only way to know who pulled what.

Only get_component_source, get_section_source and get_animation_source. Listing, searching and reading docs are unlimited.

Install the skill. It teaches the model to search first, read the docs tool, and only then pull source — which is also how you stop burning quota on components you don't keep.