# https://jsr.io/@scope/a/meta.json
{
  "versions": {
    "1.0.0": {}
  }
}

# https://jsr.io/@scope/a/1.0.0_meta.json
{
  "manifest": {},
  "exports": {
    ".": "./mod.ts"
  }
}

# https://jsr.io/@scope/a/1.0.0/mod.ts
HEADERS: {"location":"./other.ts"}

# https://jsr.io/@scope/a/1.0.0/other.ts
// This should never happen on the JSR registry. If we ever
// supported this we'd need a way for the registry to express
// redirects in the manifest since we don't store checksums
// or redirect information within the package.
console.log(1);

# mod.ts
import 'jsr:@scope/a';

# output
{
  "roots": [
    "file:///mod.ts"
  ],
  "modules": [
    {
      "kind": "esm",
      "dependencies": [
        {
          "specifier": "jsr:@scope/a",
          "code": {
            "specifier": "jsr:@scope/a",
            "resolutionMode": "import",
            "span": {
              "start": {
                "line": 0,
                "character": 7
              },
              "end": {
                "line": 0,
                "character": 21
              }
            }
          }
        }
      ],
      "size": 23,
      "mediaType": "TypeScript",
      "specifier": "file:///mod.ts"
    },
    {
      "specifier": "https://jsr.io/@scope/a/1.0.0/mod.ts",
      "error": "Redirects in the JSR registry are not supported (redirected to 'https://jsr.io/@scope/a/1.0.0/other.ts')"
    }
  ],
  "redirects": {
    "jsr:@scope/a": "https://jsr.io/@scope/a/1.0.0/mod.ts"
  },
  "packages": {
    "@scope/a@*": "@scope/a@1.0.0"
  }
}
