Incorrect x-typescript-types header when main entry is fetched directly

[marvinhagemeister]

Failing module

• GitHub: https://github.com/KaTeX/KaTeX
• npm: https://npmjs.com/package/katex

import * as katex from "https://esm.sh/[email protected]/dist/katex.mjs"

Error message

Not an error per se, but deno is unable to find the correct typings. See discussion at denoland/deno#18583

The problem is that deno resolves the main package entry itself and fetches https://esm.sh/[email protected]/dist/katex.mjs directly instead of https://esm.sh/[email protected]. The latter has the correct x-typescript-types header, but the former points to an invalid one. Given that the former is an exact match of a main entry point I was expecting the main entry point to be resolved against @types/katex.

URL	x-typescript-types	Status
https://esm.sh/[email protected]/dist/katex.mjs	https://esm.sh/v113/@types/katex@~0.16/dist/katex.mjs~.d.ts	wrong
https://esm.sh/[email protected]	https://esm.sh/v113/@types/katex@~0.16/index.d.ts	correct

katax package.json:

{
  "name": "katex",
  "version": "0.16.4",
  "main": "dist/katex.js",
  "exports": {
    ".": {
      "require": "./dist/katex.js",
      "import": "./dist/katex.mjs" // <-- This file is fetched directly by deno
    },
    // ...
  }
}

@types/katax package.json:

{
    "name": "@types/katex",
    "version": "0.16.0",
    "main": "",
    "types": "index.d.ts",
    //...
}

Additional info

• esm.sh version: latest - whatever is deployed on https://esm.sh
• Deno version: 1.32.3
• Related issue: *.d.ts file not cached denoland/deno#18583

[ije]

i believe this has been fixed in c70aa0f, will release v114 very soon

[marvinhagemeister]

Looks like it's not fully resolved. Just checked esm.sh out locally and I can reproduce the issue in main too (commit: c65507a).

[iuioiua]

Likely related: #572

[ije]

thanks for fixing this!

[marvinhagemeister]

@ije Awesome, thanks for the merge! Happy to help out!

@iuioiua Seems like that's a separate issue. I'll see if I can look into that.

[iuioiua]

That'd be amazing, @marvinhagemeister!