Get component source

Every way of getting source resolves to the same prebuilt artifact for one component, one exact version and one variant. The website, the public API and the MCP server never generate different bytes for the same selection.

Pin the version first #

Always decide on an exact version before retrieving files. Inspecting a component without a version shows its current release, but downloads and file retrieval take an exact version so that a newer release published between inspection and download cannot silently replace the one you reviewed.

If you ask for a version that does not exist you get VERSION_NOT_FOUND, never the latest release instead. If you ask for a variant that does not exist you get UNKNOWN_VARIANT together with the valid variant ids.

Options #

Copy files from the component page #

The component page lists every exported file for the selected version and variant. This suits small components and quick experiments. Copy every file listed, not just the entry file.

Download the ZIP bundle #

The bundle contains every exported file for the selection plus a README.md and a bundle.json receipt. This is the most reliable option for components with several files or assets. The layout is described in distribution.

Fetch individual files #

Artifact URLs are content-addressed by the artifact digest:

/artifacts/<componentId>/<version>/<variantId>/<digest>/manifest.json
/artifacts/<componentId>/<version>/<variantId>/<digest>/source/<path>
/artifacts/<componentId>/<version>/<variantId>/<digest>/bundle.zip

The current build serves only each component's current release; older releases are not yet retained, so a URL for a superseded release stops resolving once a newer release is published.

manifest.json is the distribution receipt. It lists every file with its path, media type, size and SHA-256 checksum, so you can check that you retrieved everything.

Ask an agent #

A coding agent connected to the MCP server can inspect a component, retrieve complete file contents when they fit the response budget, and return the bundle location otherwise. The server returns source and links; it does not write to your project. Your agent does that, with your permissions. See the agent workflow.

Verify what you received #

• Compare the file list with the receipt's files array. A component is only complete when every listed file is present at its relative path.
• Compare each file's SHA-256 with the sha256 recorded for it if you need byte-level assurance.
• Keep the receipt (bundle.json or manifest.json) next to the component, or record the component id, version, variant id and artifactDigest. That identifies exactly what you started from when you later compare against a newer release or report an issue.

After you copy the files #

You can adapt the local files under their applicable licenses. Keep source and asset notices with your copy. Upstream releases never change your copy; to adopt a newer release you retrieve it explicitly and merge your own edits.