feat: support JSR packages via jsr: prefix#41
Open
elio-Wang wants to merge 2 commits into
Open
Conversation
- Add multi-stage Dockerfile (node-server preset) - Add .dockerignore - Allow overriding git revision and Nitro preset via env vars - Document Docker usage in README Closes antfu#19
- Add `jsr:` prefix detection that resolves to JSR npm-compatible registry - Convert `jsr:@scope/name` to `@jsr/scope__name` on `https://npm.jsr.io/` - Support batching JSR and npm packages in a single request - Add optional `registry` parameter to `fetchPackageManifest` - Document JSR usage in README Closes antfu#22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
resolves #22
🔄 Context
JSR provides an npm-compatible registry at
https://npm.jsr.io/, but there's currently no way to query JSR packages through fast-npm-meta without changing the globalREGISTRY_URL(which would break npm lookups).📚 Description
Add a
jsr:prefix that automatically routes requests to the JSR npm-compatible registry.jsr:@scope/nameis resolved to@jsr/scope__nameonhttps://npm.jsr.io//vite+jsr:@luca/flag+vue@luca/flag) instead of the internal@jsr/scope__nameChanges:
server/utils/jsr.ts— prefix detection and name conversionserver/utils/fetch.ts— add optionalregistryparam tofetchPackageManifestserver/utils/handle.ts— detectjsr:prefix before parsing, pass registry info to handlerserver/routes/[...pkg].tsandserver/routes/versions/[...pkg].ts— use display name and registry from optionsREADME.md— document JSR usage