I’ve got our company’s internal design system packages published into our private NPM registry. But in doing so, I found (after I published) I needed to modify the packages for consumption by figma make. Figma’s NPM private registry would not allow me to unpublish or overwrite the package versions once I published them.
This is causing a problem in Figma Make because users are able to select old, incorrect versions of the packages when installing. I want to prevent this by being able to unpublish or delete packages from the registry, but I’m unable to do it.
We are experimenting with the best way to handle this for figma make that is easiest for our figma users--and would like to be able to hit a hard reset at some point as we may completely change strategies. Right now, we have 50 or so unbundled packages in figma make. In the future, we may want to bundle those into a single versioned package for easier consumption.
To summarize, here is a list of figma make NPM registry-related features that would help us:
- Ability to delete things from the registry (even if it's command-line)
- Ability to TEST packages pushed to our registry, or to mark them private to a specific make
- I have designers stumbling across our packages and wondering what's there
- Bug fix - make installing packages from our private figma npm registry NEVER fail authentication (retry until successful?)
- Allow installing more than one package at a time from the figma npm registry
