Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Link dual publishing #862

Open
BlackAsLight opened this issue Dec 11, 2024 · 0 comments
Open

Link dual publishing #862

BlackAsLight opened this issue Dec 11, 2024 · 0 comments
Labels
publishing Problems with publishing

Comments

@BlackAsLight
Copy link

Since it looks like there are a handful of people looking to post their libraries to both NPM and JSR, would it make sense for JSR to provide a way for them to mark that a package on NPM is the same? And in doing so allow deduplication in dependencies if one relies on the NPM one and another on the JSR one?
@github-project-automation github-project-automation bot moved this to Needs Triage in JSR Dec 11, 2024
@crowlKats crowlKats added the publishing Problems with publishing label Jan 16, 2025
@crowlKats crowlKats changed the title Link duel publishing Link dual publishing Jan 17, 2025
@crowlKats crowlKats moved this from Needs Triage to Needs Plan in JSR Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
publishing Problems with publishing
Projects
JSR
Status: Needs Plan
Milestone
No milestone
Development

No branches or pull requests
2 participants
@crowlKats @BlackAsLight