Reporting issues
What to include when you report a problem with a component, the documentation or the catalogue services, and where to send it.
Where to report #
A public support channel has not been configured for this deployment yet, so there is no support link on this page.
What to include #
A report that identifies exactly what you used can be reproduced much faster.
- Component identity: component id, exact version and variant id.
- Artifact digest: the
artifactDigestfrom the receipt (bundle.jsonormanifest.json), which proves exactly which files you started from. - Your environment: Svelte, SvelteKit and Tailwind CSS versions, browser, and whether the problem occurs during server rendering or in the browser.
- Steps to reproduce, what you expected, and what happened instead.
- Whether you edited the source. If you did, check whether the problem also happens with the unmodified files.
For MCP or API problems, include the tool or route, the input you sent, the error code you received, and any request identifier returned with the error.
Please do not include #
- Credentials, API keys, tokens or environment files.
- Personal data about your users.
- Your full project source. A minimal reproduction is more useful.
Security problems #
If a problem could affect the security of people using a component or the catalogue services, do not publish exploit details in a public report. Say that you have a security concern and ask for a private way to share the details.
Kinds of problems worth reporting #
- A component that uses a package or service it does not declare.
- Files missing from a bundle or not matching their recorded checksums.
- Accessibility problems not listed in a component's known limitations.
- Documentation that contradicts what the catalogue actually returns.