Hacker News Reader

Comment by msoad | Hacker News Reader

> --inspect-brk now works properly for esmodules

When ES Modules landed in Node? How do they work? .mjs? :(

They're available right now behind the flag `--experimental-modules`, and planned to be released without a flag in node 10.

And yes, still requires .mjs unfortunately.

https://nodejs.org/api/esm.html https://medium.com/the-node-js-collection/an-update-on-es6-m...

I sincerely hope they remove .mjs requirement. Lets not have io.js division again, all the frontend libraries are on npm and newer ones tend to use es2015 modules!

What I suspect is going to happen is that frontend people will just shrug and adopt the .mjs extension. Browsers don't care what extension you use as long as the mime type sent by the server indicates that the file is javascript.

Not exactly the entire story. Browsers don't care about the extension, true, but they still need to know whether to parse the script as a module or not, by using: <script type="module">

Hey this is cool! How come I haven't heard of <script type="module"> before.

I guess I should seriously subscribe to a newsletter or something.

How is this going to work with the gazillion existing NPM packages and projects using Babel?

Right now you just require a Babel runtime first, then use import for everything else not caring what type of modules they are. The acceptance test for proper module support in Node.js should simply have been that you can remove the Babel wrapper in an existing project that uses imports instead of requires :(

I doubt it - so long as @std/esm exists, I imagine that will continue to be the low-friction approach, especially considering how much better it is at CJS interop, supporting __dirname, __filename, etc.

Reply on news.ycombinator.com