feat: support beta/pre-release npm packages for tools#564
Merged
Conversation
Copilot
AI
changed the title
[WIP] Add support for beta packages in the tool
feat: support beta/pre-release npm packages for tools
Jun 15, 2026
Power-Maverick
approved these changes
Jun 15, 2026
Bundle Size Report 📦
Bundle Analysis ReportsThe detailed bundle analysis reports are available in the workflow artifacts:
Download the artifacts from the workflow run to view interactive visualizations. Bundle size tracking is now active! This helps prevent bundle bloat. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds opt-in installation of pre-release (beta) npm dist-tag versions of registry tools, surfaced via a contextual button on the Tool Details page — similar to VS Code's "Switch to Pre-Release Version" pattern.
Changes
Type detection
ToolRegistryEntrygainsnpmPackageName(populated from Supabasepackagenamecolumn), propagated to theToolDetailrenderer typenpm registry check (
toolRegistryManager.ts)checkBetaPackage(npmPackageName)— querieshttps://registry.npmjs.org/-/package/<name>/dist-tagsfor abetatag; usesencodeURIComponent()for correct scoped-package encoding (@org/pkg→%40org%2Fkg); returns version string ornullInstall flow (
toolsManager.ts)installPrereleaseToolFromNpm(name)— installs<pkg>@betavia pnpm, loads using base name; distinct per-step error messages (install failure vs load failure)resolvePackageDirectoryName()— strips@tag/@versionspecifiers so versioned pnpm installs (e.g.pkg@beta) resolve to the correctnode_modules/pkgdirectory; this also fixes the pre-existing debug-install bug for any versioned package specIPC / preload
CHECK_BETA_PACKAGEandINSTALL_PRERELEASE_TOOLchannels wired throughindex.ts→preload.ts→ToolboxAPITool Details UI (
marketplaceManagement.ts)checkAndShowPrereleaseButton()asynchronously checks beta availability and reveals an "Install Pre-Release Version (vX.Y.Z-beta.N)" button when abetadist-tag existsUpdate check untouched —
checkForUpdates()compares only against Supabase registry versions; beta packages are never surfaced as automatic updates