feat: add support for the jsr: protocol

[KSXGitHub]

Resolves #8941

[KSXGitHub]

Ah, so that's what they mean! Well, if it was up to me, I would have named them addParam, rawAddParam, parsedAddParam, dependencyValue, rawDependencyValue, parsedDependencyValue.

Anyway, I will fix the names that were introduced by this PR to use pref, spec, and wantedDependency correctly.

[zkochan]

🚢 10.9

[btea]

I'm not sure if this is a problem with the parsing result. When I execute pnpm add jsr:@sxzz/tsdown, the corresponding dependencies can be installed, but the content in package.json is missing. https://jsr.io/@sxzz/tsdown/0.9.1/package.json

cc @KSXGitHub @zkochan

[KSXGitHub]

@btea The JSR npm compatibility layer seems to generate its own package.json

package.json

{
  "name": "@jsr/sxzz__tsdown",
  "version": "0.9.1",
  "homepage": "https://jsr.io/@sxzz/tsdown",
  "type": "module",
  "dependencies": {
    "ansis": "^3.17.0",
    "chokidar": "^4.0.3",
    "consola": "^3.4.2",
    "debug": "^4.4.0",
    "find-up-simple": "^1.0.1",
    "pkg-types": "^2.1.0",
    "publint": "^0.3.12",
    "rolldown": "^1.0.0-beta.7",
    "rolldown-plugin-dts": "^0.8.0",
    "tinyexec": "^1.0.1",
    "tinyglobby": "^0.2.12",
    "unconfig": "^7.3.1",
    "unplugin-unused": "^0.4.4",
    "vite": "^6.3.2"
  },
  "exports": {
    ".": {
      "types": "./_dist/src/index.d.ts",
      "default": "./src/index.js"
    }
  },
  "_jsr_revision": 11
}

The links to the tarballs is in https://npm.jsr.io/@jsr/sxzz__tsdown

[KSXGitHub]

@btea npm jsr add @sxzz/tsdown also gives the same package.json:

[btea]

Looks a bit weird, I haven't used jsr before, so is this normal?

[KSXGitHub]

Looks a bit weird, I haven't used jsr before, so is this normal?

We can't do anything about it because we don't control the jsr registry.

[btea]

Got it.