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
Harmony modules aren't implemented yet, see https://nodejs.org/en/docs/es6/. As a rule of thumb, if a feature requires a flag to enable, expect it to be incomplete or broken.
Just out of curiosity, why is there even a flag to enable support for an unsupported feature? If it does nothing, it's just confusing a lot of people who're expecting import statements to work...
Reacted by Tony Gentilcore, Victor Barbu, Ruslan Konev and Tymon Oziemblewski
Alright, well, that implies that V8 does support modules to some extent, but any supported features that it exposes are inaccessible to NodeJS. Or am I wrong?
Alright, well, that implies that V8 does support modules to some extent, but any supported features that it exposes are inaccessible to NodeJS. Or am I wrong?
—
Reply to this email directly or view it on GitHub.
Activity
bnoordhuis commentedon Sep 21, 2015
Harmony modules aren't implemented yet, see https://nodejs.org/en/docs/es6/. As a rule of thumb, if a feature requires a flag to enable, expect it to be incomplete or broken.
Duplicate of #518, #2760 and probably others.
Alhadis commentedon Nov 5, 2015
Just out of curiosity, why is there even a flag to enable support for an unsupported feature? If it does nothing, it's just confusing a lot of people who're expecting
importstatements to work...Fishrock123 commentedon Nov 5, 2015
@Alhadis It comes from a dependency -- V8.
Alhadis commentedon Nov 5, 2015
Alright, well, that implies that V8 does support modules to some extent, but any supported features that it exposes are inaccessible to NodeJS. Or am I wrong?
Fishrock123 commentedon Nov 5, 2015
No it doesn't really support modules at this time. Not ES6 modules anyways.
There was some old "modules" code laying around in there and that flag enables it for testing. Or used to anyways.