When you use modules in babel, it produces dependencies. But the static syntax was designed to work alongside a rich dynamic, programmatic loader API. The problem with node in general is that top level await is problematic in many ways, and something will have to change I’m afraid, it is just the fact that the consumer of any module with a top level away will mess up the entire sync loading process in node (even if you stick to `require`). Loading a module may involve fetching code off the internet, which can’t be done synchronously. This is yet another edition of ES6 in Depth.First time here? If an import * declaration imports something with the same name as a global, like Promise, it will simply shadow the global, and it’ll be unclear what’s going on. Why Use Lodash When ES6 Is Available Lodash is a well-known JavaScript utility library that makes it easy to manipulate arrays and objects, as well as functions, strings, etc. I have previously written about using Babel to import/export ES6 modules using Node , but setting up Babel is a pain and an additional step which I would prefer avoiding whenever I can. Yeah, this keeps coming up. An important point to make is that ES6 modules export bindings, not values or references. To simplify this kind of code, there’s an all-in-one import-and-export shorthand: Each one of these export-from statements is similar to an import-from statement followed by an export. And those are the basics of modules. The fact that compilers, libraries, and tools built by the community have been able to pull everything together into a coherent system is actually really impressive, given the halfway state of things. This experiment is designed to find out the performance and resource usage of map functions of both ES6 and Lodash. :) But I eagerly look forward to seeing the dynamic APIs. [size=1] (number): The length of each chunk Returns (Array): Returns the new array of chunks. Webpack Library Example ... Node.js REPL with lodash. If you think about it, with import, each