Closed DanielRosenwasser closed 3 years ago
You're right, it has the module
field specified but the .esm.js
wasn't generated. It used to be generated but since shifting to esbuild
, it has not been properly worked on.
Ah, this is unintentional - esbuild doesn't switch import
to require
which makes sense. I think we should probably just ship as a module and see how it goes.
There's a few issues with the way the markdown-it package is published:
.js
files withimport
s - thepackage.json
needs to specify"type": "module"
if it wants to do that.import
s a non-module package (deasync
). It probably needs to switch torequire
to bring it in. As a result, I'm not sure if #54 will even work.