4 ms·

ESM modules are literally only downsides and workarounds, there is absolutely no user benefit at the moment, why would anyone adopt this technology other than a

• ratww 6y ago
  Quite the contrary. In the browser, workarounds have always been the other stopgap solutions, like script concatenation, require.js, and bundlers like Webpack. With ES6 modules, bundlers and transpilers are not mandatory anymore for a large part of modern JS development. This is a good thing, as they were a giant source of complexity.
  • londons_explore 6y ago
    Setting up a project that could either be bundled with webpack et-al, or simply hosted direct on GitHub proved tricky!
• bwindels 6y ago
  One reason is that it allows to run the same code in the browser and in node without any transpilation.
• mschuetz 6y ago
  I absolutely love ESM modules, pretty much the best thing since sliced bread. Node.js is really botching it, though, with the requirement to use the mjs extension. It makes it very awkward and cumbersome to use the same code in the browser and node.
  • Zardoz84 6y ago
    you not need to use .mjs extension if you setup correctly package.json
    • mschuetz 6y ago
      I don't want to setup a package.json for projects that don't need it.
      • afavour 6y ago
        Then yeah, you’re out of luck. But the vast majority of Node modules use a package.json so I wouldn’t say Node is “really botching it”, they’re just doing what works for the vast majority of users.