Techniques to organize JavaScript code as modules started nearly from the beginning of the JS history and went from separate files, AMD/CommonJS formats to bundlers/transpilers. Today, all the modern browsers support native JavaScript modules and they are halfway to Node.js. That means it’s a perfect time to start using them. This requires extending and optimizing the techniques we are bundling the JavaScript (aka ECMAScript, or ES) modules with today, changing the workflow and the way the code is executed. Also, it makes the new tools to develop and debug the ES modules. Today it’s possible to load script synchronously, on demand and publish them to production, making sure all the code is still fully functional.
Expect to hear about the main differences of the native modules (comparing to the bundlers/transpilers approach), how they work, and their features; how the browser/Node.js engines load and execute them and why it took so long for ES modules to be implemented in the JS engines; how to use native JS modules in production today; the benefits, performance overview, pros/cons, and conclusions; an overview of future perspectives and a number of examples/demos.