Skip to main content
Package resolution types are used to retrieve all component and asset data needed to render content. Choose between full resolution (simpler) or reference resolution (efficient caching).

ResolvedPackage

Full package data with all resolved dependencies inline.
Use when you want all data in a single request:

ResolvedPackageRef

Package IDs only, for normalized caching.
Use for efficient caching (smaller payloads):
Response:
Then fetch package data separately using resolvedPackageData.

ResolvedPackageData

Package data identified by content-addressed hash.

Components Field

JSON object with component name as key and compiled code as value:

Assets Field

JSON object with component name as key and asset array as value:

Draft Package IDs

Draft packages use a special ID format instead of a content hash:
Example: draft:proj123:org456
Draft packages should not be cached long-term as they change frequently during development.

Caching Strategy

Content-addressed IDs (SHA-256 hashes) mean published packages never change:
  • Package - Package type with resolution fields
  • Content - Content with resolved packages