Skip to content

Suggestion: Proxying to another JSR API #248

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

Closed
jollytoad opened this issue Mar 8, 2024 · 1 comment
Closed

Suggestion: Proxying to another JSR API #248

jollytoad opened this issue Mar 8, 2024 · 1 comment

Comments

@jollytoad
Copy link
Contributor

To allow the use of private or local registries the JSR API should be capable of proxying to another instance, eg the public one.

I wanted to run a local JSR so that I could preview my package and get it into shape before publishing to the public JSR, but having to also publish dependencies (such as @std packages) is a real pain. Ideally my local JSR could proxy to the public one to avoid this. This would also open up the opportunity to run a private JSR, or even a JSR for testing packages in other runtimes (#179).

@github-project-automation github-project-automation bot moved this to Needs Triage in JSR Mar 8, 2024
@lucacasonato lucacasonato moved this from Needs Triage to Needs Plan in JSR Nov 8, 2024
@lucacasonato
Copy link
Member

I am going to close this as a duplicate of #203

@github-project-automation github-project-automation bot moved this from Needs Plan to Done in JSR May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants