Failed to import - many-keys-weakmap | Dropped support for .js vs mjs extension

[pankgeorg]

Failing module

• npm: https://www.npmjs.com/package/many-keys-weakmap/v/1.0.0

import ManyKeysWeakMap from "https://cdn.esm.sh/v64/[email protected]/es2021/many-keys-weakmap.js"

Error message

After onload I got this:
404

Additional info

• esm.sh version: 64
• Browser version: Chrome 115 (latest)

---

So I think the problem is that at some point, support for the .js extension was dropped. The above link works with .mjs. This causes a few issues at the Pluto community where people have deployed versions of this without the m :(

[ije]

the path structure has been changed, please use below urls:

import ManyKeysWeakMap from "https://esm.sh/v64/[email protected]?target=es2021"
// or
import ManyKeysWeakMap from "https://esm.sh/v64/[email protected]/es2021/many-keys-weakmap.mjs"

[pankgeorg]

Thanks for your time looking into this! We will use the new in any future work, but users of old versions of Pluto have static HTML that point to the .js version on version /v64. These HTML files are deployed already and are not controlled by us - updating these will require user action. Is it possible for version 64 to respond to the .js endpoints as it used to?

[pankgeorg]

We're using this style: fonsp/Pluto.jl@8d63bde and fonsp/Pluto.jl#2514 with the pin argument. Does it look ok?

[ije]

i am adding a workaround to redirect the old url the new url.

[ije]

will deploy the patch after testing pass

[pankgeorg]

Thank you!

[ije]

should works now

[pankgeorg]

should works now

Thanks a ton! I can see the response in cURL from a US server (my browser has a Greek/EU IP so is still getting the old value from cloudflare 😅, but I have faith in cache invalidation!!)

[ije]

oh sorry, i am going to purge the cache

[ije]

done, would you like to try again 🙏

[pankgeorg]

yes! works like a charm, thanks!!