Skip to content
PageSugar 111 components
Search components
Docs Site navigation
Documentation menu, current page: Help and issue reports

Help and issue reports

What to include when you report a problem with a component, the documentation or the catalogue services, and where to send it.

Published
View as Markdown
On this page

Where to report#

A public contact route is not available yet. The checklist below helps you collect a useful report; keep it locally until a reporting destination is published.

From your coding agent#

If your agent is connected to the MCP server, it can send a comment about a component straight to us: tell it what you think and ask it to pass the comment on. It sends the exact component version with it. See Feedback for what happens to the comment.

What to include#

Start with the component page, what you expected and what happened. Add the details below when you have them; a clear reproduction is more useful than a long report.

  • Component identity: component id, exact version and variant id.
  • Artifact digest: the artifactDigest from the receipt (bundle.json or manifest.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. Use a confirmed private contact route before sharing sensitive details. If no route is available, keep those details private.

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.