TypeScript interfaces for component mapping
For developers
Enterprise plans
Deprecated
Builder.io is transitioning from manual component mapping to Component indexing, which automatically discovers and maps your design system components.
To migrate away from component mapping, visit the Component mapping migration guide.
When working with TypeScript, you can leverage these interfaces for better type safety in your mapping functions:
When creating a mapping function for a specific component, you should extend BaseFigmaProps with the properties from your Figma component:
CLI command reference
With these mapping capabilities, you can create an efficient design-to-code workflow that maintains consistency between your Figma designs and your Angular components. Use these commands at the command line.
Generate mappings:
Publish mappings:
Migrate existing mappings:
Re-authenticate:
figma generate
The figma generate command supports several options:
--scaffold: creates basic mapping templates when automatic generation fails.
--verbose: provides more detailed output during the mapping process.
--output: specifies the output directory for generated mappings.
--ci: run in non-interactive mode for CI/CD environments.
For more details on the commands available to you from the CLI, visit Builder CLI API, specifically the section on Figma commands.
What's next
- For an overview of how to connect Figma components to code components, go to Map components.
- For more information on the mapping process, publishing, and CI best practices, go to Component mapping in depth.
- For framework-specific details, go to Component mapping examples.