ESM Support about isomorphic-dompurify HOT 4 OPEN

Thank you @shishkin for experimenting with this. If adding new formats doesn't help, there is no much I can help with.
Let's keep this issue open in case anyone else comes up with a solution.

from isomorphic-dompurify.

Hi @shishkin ,

Thank you for your suggestion. It makes sense.

The isomorhic-unfetch uses microbundle for this purpose, like this:

// package.json
{
    "build": "microbundle src/index.mjs -f cjs,esm,umd && microbundle polyfill/polyfill.mjs -o polyfill/index.js -f cjs --no-sourcemap"
}

However, I'm not sure if the package will work for Deno anyway because of the JSDom dependency which may not work for everywhere.

Anyway, would you like to help with this improvement?

from isomorphic-dompurify.

I gave it a try but ultimately wasn't able to figure out dynamic imports in the isomorphic ESM case.

After looking at isomorhic-unfetch again, it seems it benefits from the unfetch default export being an async function returning a Promise. That makes it easy to call a dynamic import and chain the promises for a result.

In case of DOMPurify, the default export is an object with functions. And I wasn't able to construct a static export from dynamic imports as I wasn't able to unwrap promises without top level await. And top level await seems only supported on specific targets, so won't cover default ESM case.

Please let me know if I have missed something.

from isomorphic-dompurify.