Figma Make auto check of new Design System NPM Version

I would love to have my Figma Make Template that i created, that ingested our Design System via private NPM, to check if there are newer Versions of the NPM package present. Therefore I asked the AI if this would be possible and got the following response - it would be great to have the option to let the AI check if any new package is available, so template users can update to new versions.

AI’s Repsonse:

list_private_packages tool fails despite working registry

Environment: Figma Make (web app builder)

Summary: The list_private_packages platform tool returns a generic failure when called by the AI assistant, even though the private npm registry is properly configured and fully functional for installs.

Registry configuration (from /tmp/sandbox/.npmrc):

@tuvsud:registry=https://registry.figma.com/npm/47b70d29-1b38-4307-bc23-1c0fda0d77f3/registry/
//registry.figma.com/npm/47b70d29-1b38-4307-bc23-1c0fda0d77f3/registry/:_authToken=figi_<redacted>

Evidence that the registry works:

• install_package @tuvsud/design-system@latest — succeeds, resolves and installs the correct package from the private feed
• install_package @tuvsud/design-system@1.15.1-alpha-2 — succeeds, installs the specific version
• Both prove: DNS resolves, auth token is valid, the Figma proxy reaches the upstream Azure DevOps Artifacts feed, and packages download correctly

What fails:

• list_private_packages (with or without nextToken) — returns a generic failure with no useful error message. No package list is returned.

Expected behavior: The tool should return a list of packages available in the configured private registry (at minimum @tuvsud/design-system and its published versions).

Impact: Without this tool, the AI cannot programmatically check which versions of the design system are available. We've implemented a workaround using install_package @latest to detect newer versions, but this actually installs the package rather than performing a read-only query — it's a blunt instrument where a scalpel is needed.

Reproduction steps:

1. Create a project from a template that has a private npm registry configured (Design System Registry dropdown)
2. Confirm installs work: ask the AI to run install_package for a package from the private registry
3. Ask the AI to call list_private_packages
4. Observe: generic failure, no packages returned

Feature Request: Read-only package version query tool

Summary: Please add a tool (e.g., list_package_versions) that queries a configured npm registry and returns available versions + dist-tags for a given package, without installing anything.

Use case: Our design system template needs to detect at conversation start whether a newer DS version is available. Currently the only tool that talks to the registry is install_package, which has the side effect of actually installing the package. A read-only query tool would allow:

• Checking available versions without modifying node_modules or package.json
• Showing the user a list of versions they could upgrade to
• Comparing latest dist-tag against the installed version
• Making smarter decisions about whether an update is safe

Suggested API:

list_package_versions({
  packageName: "@tuvsud/design-system"
})
// Returns: { versions: ["1.14.0", "1.15.0", ...], distTags: { latest: "1.15.1", next: "1.16.0-beta.1" } }