Builder is transitioning from manual component mapping to component indexing, which automatically discovers and maps your design system components.
We recommend all customers migrate to Component indexing.
- Component mapping will be removed from the platform.
- Component indexing is faster and provides the same benefits as component mapping.
Component indexing eliminates the 7-step manual mapping workflow. Instead of creating .mapper.tsx files, publishing them, and maintaining them manually, you simply run one command to automatically discover your components.
Complete the following steps to migrate away from component mapping.
Delete all .mapper.tsx, .mapper.ts, .mapper.jsx, and .mapper.js files from your repository.
Run the publish command without any mapper files to remove your existing mappings from your Builder space:
npx "@builder.io/dev-tools@latest" figma publishYou cannot use both component mapping and component indexing simultaneously.
Run the indexing command from your project root or design system repository:
npx "@builder.io/dev-tools@latest" index-repoThis automatically discovers your components and uploads them to your Builder space.
Continue using the code command as before. Your generated code will now use the automatically discovered components:
npx "@builder.io/dev-tools@latest" code --url "figma-url"For more details, see the Component indexing documentation.