Skip to main content
Question

Figma Make do not want to use open NPM packages

  • April 20, 2026
  • 1 reply
  • 46 views
Lasse Febakke Straum

I am trying to set up a Figma Kit for our organization. We have a public design system that is available for everyone to use. When I try to add it to the package.json it will not be able to install it as it is not in the Figma NPM registry. Figma make can edit the .npmrc file and remove the Figma registry. But Figma will overwrite this all the time. For instance, if I try to publish the kit. It will fail as Figma will overwrite this value and look for it in the Figma registry. 

I found a workaround where I tell Figma make to install and change the settings for each time someone uses the Kit. But this seems unnecessary and weird when using public NPM packages. Am I doing something wrong or is this the intended behavior for Figma Make? 

 

Edit: The workaround is fragile. In most cases Figma make will want to style shadcn components instead of dealing with jumping trough hoops to get public packages installed. 

 

    1 reply

    ksn
    Figmate
    • ksn
    • Community Support
    • April 23, 2026

    Hey ​@Lasse Febakke Straum - thank you for checking in on this. Can I ask some question, just to make sure I’ve understood some aspects of your post correctly.

    What’s the actual error when you try to install/publish?

    Is the package scoped or unscoped?

    If you try a simple, random npm package, does that go through no problem, or still hits issues you’re seeing?

     

    Terms & ConditionsCookie settingsAccessibility statement