You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The esm.sh service rewrites all the module.exports + require stuff to proper ES6 modules.
Would it be an idea to publish ES6 modules directly, such that this can be used from unpkg.com etc?
The text was updated successfully, but these errors were encountered:
Hi @borkdude 👋
That sounds useful! Makes me happy to see this library being used 🙂
I haven't worked with ES6 modules before. What do we have to change to make them work? Any hints how to do that are very welcome. I suppose it's possible to support ES6 modules while also keep supporting Node.js and Typescript, right? If it's easier for you to just open a PR, you are also more than welcome 😊
I'd like to use this library in the squint playground. It seems I'm only able to do this via esm.sh:
example
The esm.sh service rewrites all the module.exports + require stuff to proper ES6 modules.
Would it be an idea to publish ES6 modules directly, such that this can be used from unpkg.com etc?
The text was updated successfully, but these errors were encountered: