TypeScript: imports in a Deno project resolve to nothing #1984

Symptom

In a TypeScript project run by Deno (a deno.json or deno.jsonc, usually no tsconfig.json and no node_modules), almost every import resolves to nothing:

• an import-map entry ("@/": "./src/", "lib": "jsr:@scope/lib@^1") is UNRESOLVED
• a workspace member imported by its name (@scope/member, @scope/member/sub) is UNRESOLVED, so every call across members is matched by name only
• jsr: and npm: specifiers, and https: imports, are UNRESOLVED, and their packageName is wrong (https:, npm:pkg@^3)
• --library auto finds no dependency at all, because Deno keeps them in its own cache rather than node_modules

On a public Deno web app (67 files, 333 imports), 266 of the 333 imports disagreed with deno info --json, and the graph had no call into any dependency.

Only relative ./x.ts imports resolve today.

Expected

Imports resolve as Deno resolves them, and --library auto stages what a Deno project imports. A project with no Deno config is unaffected.