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
If I set the type field to commonjs, the gulpfile.esm.js file works as expected (but not my code which uses only ES modules).
It would be nice if interpret could manage this case (i.e. that the new ESM parser is already enabled).
The text was updated successfully, but these errors were encountered:
I'm using the new ES modules features from Node.js 12 (the next LTS).
If I set my package to be an ESM one with the field
type
set tomodule
inpackage.json
file, thegulpfile.esm.js
file stops working as expected.If I set the
type
field tocommonjs
, thegulpfile.esm.js
file works as expected (but not my code which uses only ES modules).It would be nice if
interpret
could manage this case (i.e. that the new ESM parser is already enabled).The text was updated successfully, but these errors were encountered: