fast-npm-meta

🔗 Linked issue resolves #22 🔄 Context JSR provides an npm-compatible registry at , but there's currently no way to query JSR packages through fast-npm-meta without changing the global (which would break npm lookups). 📚 Description Add a prefix that automatically routes requests to the JSR npm-compatible registry. is resolved to on Batching with npm packages works: Response returns the original JSR name (e.g. ) instead of the internal Changes: New — prefix detection and name conversion — add optional param to — detect prefix before parsing, pass registry info to handler and — use display name and registry from options — document JSR usage

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 #19 🔗 Linked issue resolves #19 🔄 Context Currently the server is hardcoded to the preset with no official way to self-host. Users who want to deploy on their own infrastructure need a Docker image. 📚 Description Add a multi-stage Dockerfile that builds the server with the Nitro preset, producing a minimal production image containing only Node.js and the compiled directory. Changes: Dockerfile: 3-stage build (deps → build → runtime), final image based on .dockerignore: exclude , , , etc. server/nitro.config.ts: allow and env var overrides, with try-catch fallback for in environments without README.md: add Docker build & run instructions with environment variable reference