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
Thank you for your work on this project. It is (nearly) perfect for my use case. I'm authoring a pure ESM library in typescript, so the addition of file extensions to imports is very very nice.
However, I've seemed to find a bug... If import statements are over multiple lines, the file extensions does not seem to be resolved in the output (making the ESM dist incompatible with Node and the browser).
Thank you for your work on this project. It is (nearly) perfect for my use case. I'm authoring a pure ESM library in typescript, so the addition of file extensions to imports is very very nice.
However, I've seemed to find a bug... If import statements are over multiple lines, the file extensions does not seem to be resolved in the output (making the ESM dist incompatible with Node and the browser).
Example
This is the commit where I changed imports and things started working correctly: manzt/zarrita.js@
bd6706a
(#29)The text was updated successfully, but these errors were encountered: