Skip to main content
HeatherSimpsonMayfield
New Member
May 20, 2026
Question

Make Kit - No components were extracted from this library

  • May 20, 2026
  • 15 replies
  • 322 views

I have a design library with styles, tokens, variables, components etc all set up and published.

I’m trying to use this to create a kit in Figma Make but when I choose the design library, when I click in the components folder, it says ‘no components were extracted from this library’ and I don’t know why.

15 replies

Yogesh Arora
New Member
July 15, 2026

Hey ​@Jaycee Lewis 

I am kind of in the same boat. But the experience is a bit confusing here for me. Am attaching a screenshot for that explanation.

  1. I am doing a POC with Carbon design system
  2. Published it and create a kit using “Library style”
  3. I dont see any components from Carbon in the Components folder as such, but when i tried building a page, i checked the code for that page and there in, it refers to components being imported from Carbon/React.

Is it the case that, the components are not shown as such in any folder, but when we build, if a page is using any, it will simply import those components via code.

Could this be confirmed? Bigger question of course is, if we just create a Make kit using “LIbrary Styles” are the components by default also accessible OR these could be accessible only through “NPM Package” route.

 

 

Jaycee Lewis
Figmate
Figmate
July 22, 2026

Hi, ​@Yogesh Arora 👋 Let me do some digging for us and I’ll try to follow up here by the end of the week. Thanks! — Jaycee

Jaycee Lewis
Figmate
Figmate
July 22, 2026

Hey ​@Yogesh Arora  👋 Great question — and observation.

When you create a kit using "Library Styles," Figma Make extracts your library's CSS styles — colors, typography, spacing, and tokens — and delivers them as a styles.css file inside the kit. It does not extract your components. That's why you don't see a Carbon components folder in the kit.

So to your bigger question: components are not accessible by default through the Library Styles route. To bring in actual components, you need the NPM Package route.

- Library Styles → styles and tokens (styles.css + guidelines)
- NPM Package → the actual production components

Basically, code components come through the npm package route while styles/tokens come through the library.

Docs for reference:

Please let me know if you need any additional help! — Jaycee

Yogesh Arora
New Member
August 11, 2026

Hello ​@Jaycee Lewis 

 

Thanks for the response. A question:

How can i install a Design system, which i have purchased through a license, I am guessing thats not a simple process perhaps as you mentioned through NPM package. The one in above thread was Carbon, which is open sourced, so was easy for Figma Make to fetch online.

Jaycee Lewis
Figmate
Figmate
August 13, 2026

Hi, ​@Yogesh Arora 👋 Thanks again for the great question and follow up.

I need to update my previous reply — the @carbon/react imports you saw weren't your Library Styles kit delivering components. In Figma Make, "the model can install and use npm packages on your behalf as it builds your application" (Working with npm)

Library Styles genuinely only brings styles. If you check the code view, your library folder contains a guidelines folder and a styles.css file, nothing more — see the "How do I know what the Make kit is using from my library?" FAQ in Get started with Make kits.

A licensed system usually isn't on the public registry, and Make can't pull it the same way.

Two questions:

  • How does your vendor distribute it — public npm, a private registry with an auth token, or a tarball?
  • What plan are you on? Publishing to Figma's private npm registry runs through Admin → Resources → npm registry, and scope management needs an admin

Thanks! — Jaycee