Skip to content

feat: support for yarn protocol jsr: #289

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.

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

Open
2 of 4 tasks
jkowalleck opened this issue Apr 10, 2025 · 1 comment · May be fixed by #293
Open
2 of 4 tasks

feat: support for yarn protocol jsr: #289

jkowalleck opened this issue Apr 10, 2025 · 1 comment · May be fixed by #293
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@jkowalleck
Copy link
Member

jkowalleck commented Apr 10, 2025

Is your feature request related to a problem? Please describe.

since yarn 4.9.0 they have native support for protocol jsr. see https://github.com/yarnpkg/berry/releases/tag/%40yarnpkg/cli/4.9.0

lets add support for it!

Describe the solution you'd like

JSR packages have the download location have the "correct" (whatever this means) properties:

test bed should be a new one called jsr-protocol-dependency!

Describe alternatives you've considered

/

Additional context

Contribution

  • I am willing to provide an implementation
  • I will wait until somebody else implements it
@jkowalleck jkowalleck added enhancement New feature or request help wanted Extra attention is needed labels Apr 10, 2025
@jkowalleck jkowalleck changed the title feat: yarn jsr support feat: support for yarn protocol jsr: Apr 10, 2025
@jkowalleck jkowalleck linked a pull request Apr 10, 2025 that will close this issue
@jkowalleck
Copy link
Member Author

a kickstart was made, by adding test beds and initial test snapshots: #293
the PR might be abandoned, feel free to continue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant