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

Cache original metadata response without rewriting #24

Open
victorb opened this issue Apr 25, 2019 · 0 comments
Open

Cache original metadata response without rewriting #24

victorb opened this issue Apr 25, 2019 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@victorb
Copy link
Member

victorb commented Apr 25, 2019

Currently, when retrieving a new package from npm registry, Open-Registry rewrites the URL of the tarball to point to Open-Registry and then saves the package to cache.

Instead, we should allow more flexibility, and write both the changes metadata + the original, so if in the future we decide to point the tarball somewhere else, we can change it on runtime.

@victorb victorb added bug Something isn't working good first issue Good for newcomers labels Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant