CSS link from README is dead

[Sorokin-Anton]

<link rel="stylesheet" href="https://esm.sh/@wooorm/starry-night@3/style/both">

from README points to 404

[wooorm]

It's a bug in esmsh, you can report it there

[kilianc]

this is still true

[wooorm]

do you want to raise it upstream?

[kilianc]

do you want to raise it upstream?

I don't know if you are trolling or not.

This does not see to be a bug in esmsh, but I don't know how esmsh works. What I know is that adding .css solves the issue: https://esm.sh/@wooorm/starry-night@3/style/both.css.

I'll open a PR.

[wooorm]

I am not trolling. You are ignoring what I am saying. It is a bug in esmsh.

[wooorm]

inb4: with ESM, with export maps, we have arbitrary URLs. I could decide that the API is xxx/foo-bar-baz. esmsh should map that to some file from the export map, say ./path/to/alpha-bravo-charlie.css, but it doesn’t matter where that file is on the file system. Based on that file, esm.sh can infer if that file is JavaScript or CSS or whatever.
But xxx/foo-bar-baz.css is not the API.

[kilianc]

You are ignoring what I am saying. It is a bug in esmsh.

I am not ignoring what you are saying, I am trying to help. The link in your readme is broken and I opened a PR to fix it. Looks like it's a fix that doesn't work for you, which is completely ok.

At least people that stumble upon this issue can read this thread and use my workaround.

I understand that xxx/foo-bar-baz.css is not the API, but I don't think users to this repo care, they try to use your project. Would you be open to documenting this in the README or is your stand to leave it broken until esm.sh fixes it?

[wooorm]

I understand that xxx/foo-bar-baz.css is not the API

It’s not a good workaround, when esmsh fixes this bug that workaround will break.
Export maps encapsulate APIs. Users can’t access arbitrary files inside packages with export maps.