Skip to content

fix: keep scoped package slash in generated install URLs#478

Closed
YuF-9468 wants to merge 1 commit intostackblitz-labs:mainfrom
YuF-9468:fix/install-link-scope-separator
Closed

fix: keep scoped package slash in generated install URLs#478
YuF-9468 wants to merge 1 commit intostackblitz-labs:mainfrom
YuF-9468:fix/install-link-scope-separator

Conversation

@YuF-9468
Copy link

@YuF-9468 YuF-9468 commented Mar 5, 2026

Summary

Fixes the scoped package install URL formatting issue reported in #477.

When release package names are reconstructed from storage keys, scoped packages were kept in normalized @scope:pkg form. This propagated to generated install commands and produced invalid URLs.

This change converts normalized separators back to npm package form (/) before rendering release text, so generated install commands use @scope/pkg correctly.

Verification

  • Updated package-name reconstruction logic in packages/app/server/api/repo/commits.get.ts.

@btea
Copy link
Contributor

btea commented Mar 6, 2026

It seems to be a duplicate of #474.

@YuF-9468
Copy link
Author

YuF-9468 commented Mar 6, 2026

Thanks for the heads-up — I checked this again, and you’re right: this PR overlaps with #474 (same fix intent for scoped package slash handling). To keep discussion and history in one place, I’m closing this as a duplicate of #474.

@YuF-9468 YuF-9468 closed this Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants