Why does deno info outputs / after : in package names

[kuchta]

It's not consistent with general use of package names in deno

[bartlomieju]

Can you show an example of such output?

[kuchta]

Sure

: deno info npm:tailwindcss                                                                       10/16/2024 02:58:25 PM
dependencies: 106 unique
size: 14.79MB

npm:/[email protected] (5.44MB)
├── npm:/@alloc/[email protected] (13.77KB)
├── npm:/[email protected] (13.34KB)
├─┬ npm:/[email protected] (88.09KB)
│ ├─┬ npm:/[email protected] (9.43KB)
│ │ ├── npm:/[email protected] (9KB)
│ │ └── npm:/[email protected] (87.84KB)
│ ├─┬ npm:/[email protected] (43.59KB)
│ │ └─┬ npm:/[email protected] (16.35KB)
│ │   └─┬ npm:/[email protected] (22.4KB)
│ │     └── npm:/[email protected] (9.39KB)
│ ├── npm:/[email protected] (169.16KB)

[kuchta]

Thank you for clarification, Bartek. But actually both are valid URLs (URIs) parsable by new URL() just one with pathname starting with a slash while the other is not which is kind of confusing considering they are not absolute paths, but I think if you generally prefer one form over the other it's better to be consistent in the output with the recommended input (interface)

[BlackAsLight]

Thank you for clarification, Bartek. But actually both are valid URLs (URIs) parsable by new URL() just one with pathname starting with a slash while the other is not which is kind of confusing considering they are not absolute paths, but I think if you generally prefer one form over the other it's better to be consistent in the output with the recommended input (interface)

Neither start with a slash. It starts with npm:/. What I believe he is saying, like the HTTPS links starts with http://, this link starts with npm:/.

[kuchta]

No, URLs (URIs) don't start with scheme:/ and neither with scheme:// unless there's a optional authority (host) section present. See: https://en.wikipedia.org/wiki/URL

> new URL('npm:/[email protected]')
URL {
  href: "npm:/[email protected]",
  protocol: "npm:",
  pathname: "/[email protected]",
}
> new URL('npm:[email protected]')
URL {
  href: "npm:[email protected]",
  protocol: "npm:",
  pathname: "[email protected]",
}

[0f-0b]

If the path of a URL does not start with a slash, it is said that the URL has an opaque path. The ways you can work with such URLs are very limited. For example when resolving a relative URL, if the base URL has an opaque path, the input can only be a #fragment or an absolute URL.

new URL("bar", "npm:package/foo").href; // throws. "bar" is neither a fragment or an absolute URL
new URL("bar", "npm:/package/foo").href; // returns "npm:/package/bar"

I guess this is why the change was made.

[kuchta]

Thank you for clarification, @0f-0b ❤️. If you work with it like this, then it makes total sense. But I still think this format shouldn't be part of user interface unless it's used in documentation and unless it's also preferred format on the input side where you have to sanitize it anyway. Should I create an issue for that?