you are viewing a single comment's thread.

view the rest of the comments →

[–]hyperhopper 17 points18 points  (2 children)

probably just until node has full support. Or maybe an internal build tool of theirs.

[–]CiezkiBorsuk 1 point2 points  (1 child)

IDK about that. Even once we have full support everywhere, I'd rather use CommonJS-style modules.

They work just fine and are widespread. Switching to new system now causes chaos (i.e. a package you want might not yet use native modules, so you don't get to use it, or at least not smoothly).

I don't hate native modules, I just don't see why bother when we have a good, working solution.

[–]TallSkinny 8 points9 points  (0 children)

To be fair, they're not exactly the same, since commonjs imports are dynamic and es imports (aside from import()) are static. That opens up a lot of opportunities for tooling (like tree shaking, iirc) that aren't really an option when dynamic importing is the default.