Setting the file. One moment.
Skill 24 · Hyperframes Registry
Subchapter 24.5
references/install-locations.mdMarkdown1 KBView on GitHub
| Item type | Default install path | Configured by |
|---|---|---|
| Block | compositions/<name>.html |
hyperframes.json#paths.blocks |
| Component | compositions/components/<name>.html | hyperframes.json#paths.components |
The target field in each item’s registry-item.json specifies a default install path. The add command remaps the prefix based on hyperframes.json#paths:
compositions/ get remapped to <paths.blocks>/compositions/components/ get remapped to <paths.components>/Created automatically by hyperframes init. If it doesn’t exist when you run add, the CLI creates it with defaults:
{
"$schema": "https://hyperframes.heygen.com/schema/hyperframes.json",
"registry": "https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry",
"paths": {
"blocks": "compositions",
"components": "compositions/components",
"assets": "assets"
}
}To install blocks into a scenes/ directory instead of compositions/:
{
"paths": {
"blocks": "scenes"
}
}Then hyperframes add data-chart writes to scenes/data-chart.html instead of compositions/data-chart.html. The snippet output reflects the remapped path.