Repository navigation
require('some-es-package') does not fail as expected #325
Description
Activity
See nodejs/node#27417 and #320.
The short answer is that the behavior of
requirewith respect to ESM files and packages is still a work in progress.Reacted by Tobias NießenThe call to require() fails with a syntax error whereas it becomes ERR_REQUIRE_ESM if I rename index.js to index.mjs. Is this behavior intended?
Slightly more full answer: Yes and no. The behavior will likely change. It should ideally be
ERR_REQUIRE_ESMin both cases, or not an error in either case. Moving from the (likely) parse error to the much nicer and more explainativeERR_REQUIRE_ESMerror (or to not an error) hasn't really been seen as a semver breaking change, so fixing that up one way or another (which entails closing in on our final cjs interop strategy) hasn't been looked at much (sicne we're either just changing the text of a (likely) error to a better one or removing the errors entirely). In both cases, our logic for package-scoped configuration (for recognition of thetypefield) needs to get baked into the cjs resolver (as right now it is not) - our current implementation pretty much doesn't touch the cjs resolver, which is also why we just had to emergency patch in throwing on.mjsrequire's without the flag set.Reacted by Tobias Nießen
First of all, thanks to all of you for your efforts! I am currently playing around with Node.js 12.0.0 and the new ESM implementation. One thing I have come across is that
require('some-es-package')does not fail as expected ifsome-es-packagehas apackage.jsonfile containing these properties:The call to
require()fails with a syntax error whereas it becomesERR_REQUIRE_ESMif I renameindex.jstoindex.mjs. Is this behavior intended?