jsr adds an extra slash for named exports `jsr:/@std/path@1.0.8/posix`

[inverted-capital]

That slash is actually fine - jsr: and jsr:/ are equivalent :)

The same also applies to npm: and npm:/.

Originally posted by @lucacasonato in #400

I am having an issue with this, as it breaks installs in stackblitz.com.

In stackblitz, any imports that do not have this additional slash at the front work fine, but with the slash it fails to install using npx jsr add.

If jsr: and jsr:/ are equivalent, then could jsr pretty please just output jsr: consistently, to ease the integration with other parts of the ecosystem ?

[inverted-capital]

to be clear, the issue only seems to occur when the jsr module I am installing has a dependency on a jsr module that is a named export.

The module I published that exhibits this behaviour is here: https://jsr.io/@artifact/tip/0.0.20/shards.ts

[inverted-capital]

furthermore ! I have noticed that this dummy slash insertion only occurs for named exports that are coming from a deno.json that does not have an explicit import for the named import

So for this line to be output without the offending slash:

import { hc } from 'jsr:@hono/hono@4.7.7/client'

I added this line in my deno.json in the workspace root:

    "hono": "jsr:@hono/hono@4.7.7",
    "hono/client": "jsr:@hono/hono@4.7.7/client",  // <-- added this and the problem resolves

I am not sure if being in a workspace or not has any bearing on the issue, but in my case, I am using a workspace.