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.

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

per-scope JSR_URL #23594

Open
teidesu opened this issue Apr 28, 2024 · 1 comment
Open

per-scope JSR_URL #23594

teidesu opened this issue Apr 28, 2024 · 1 comment
Labels
jsr Issues or feature requests relating to JSR.io

Comments

@teidesu
Copy link

teidesu commented Apr 28, 2024

in many cases it makes sense to have a separate registry limited to a single scope, similarly to how it's possible in npm

the use-cases for this range from enterprise packages published to a self-hosted instances to various kinds of integration tests, and would also allow to not "populate" the local jsr instance with upstream packages in many cases.

with npm we can use either .npmrc or an env variable npm_config_@scopename:registry

i suggest deno should support something similar with the JSR_URL env variable, something like JSR_URL_mycompany=https://jsr.mycompany.org maybe?

and ideally this should also be persisted somewhere, not just an env variable, but that's probably for another feature request

@marvinhagemeister marvinhagemeister added the jsr Issues or feature requests relating to JSR.io label Apr 29, 2024
@teidesu
Copy link
Author

teidesu commented May 7, 2024

someone suggested that a nice solution for this might be supporting something along jsr://<domain>/<scope>/<name>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jsr Issues or feature requests relating to JSR.io
Projects
None yet
Development

No branches or pull requests

2 participants