Summary
Allow Figma Make to read an .npmrc file so teams can install and use internal or private scoped packages (e.g., @company/components) within their projects.

Problem
Our organization maintains internal web component libraries that align to our design system in Figma. These components are published as scoped npm packages (e.g., @ourorg/design-system). Currently, Figma Make does not support .npmrc configuration or scoped package resolution, which prevents us from using our own code directly in Figma Make. It would also reduce the amount of code Figma make generates if it doesn’t have to generate common component code.

Impact
Without this support, designers cannot easily work with the same components developers use in production. This creates a disconnect between design and code, increases manual work, and raises the risk of inconsistencies.

Proposed Solution

• Enable Figma Make to read .npmrc configuration files for authentication and registry settings.

• Support installation of scoped packages (e.g., @org/package) from private or internal npm registries.

• Allow these packages to be used just like public npm packages within Figma Make.

Benefits

• Ensures design and development teams stay aligned by using the same component libraries.

• Improves consistency and speeds up iteration by removing the need to manually replicate internal components.

• Unlocks broader adoption of Figma Make for organizations with established design systems.