es6-module-loader

I've tried searching the internet for the execution order of imported modules. For instance, let's say I have the following code: import "one" import "two" console.log("three"); Where one.js and two.js are defined as follows: // one.js console.log("one"); // two.js console.log("two"); Is the console output guaranteed to be: one two three Or is it undefined? McMath Imported ES6 modules are executed asynchronously . However, all imports are executed prior to the script doing the importing. This makes ES6 modules different from, for example, Node.js modules or <script> tags without the async

I use webpack path aliases for ES6 module loading. E.g. If I define an alias for utils instead of something like import Foo from "../../../utils/foo" , I can do import Foo from "utils/foo" The problem is that once I start using aliases, WebStorm looses track of the import and I'm left with warnings and no auto-completion. Is there a way to instruct WebStorm to use such aliases? [Deprecated answer. Starting since WS2017.2 Webstorm automatically parses and applies Webpack config (see @anstarovoyt comment)] Yes, there is. In fact, Webstorm can't automatically parse and apply Webpack config, but

I've been working through Webpack tutorial . In one of the sections, it gives the code example that contains one line of essence to this question: export default class Button { /* class code here */ } In the next section of said tutorial, titled "Code splitting", the class defined above is loaded on demand, like this: require.ensure([], () => { const Button = require("./Components/Button"); const button = new Button("google.com"); // ... }); Unfortunately, this code throws an exception: Uncaught TypeError: Button is not a function Now, I know that the right way to include ES6 module would be

EDIT: for more background, also see the discussion on ES Discuss . I have three modules A , B , and C . A and B import the default export from module C , and module C imports the default from both A and B . However, module C does not depend on the values imported from A and B during module evaluation, only at runtime at some point after all three modules have been evaluated. Modules A and B do depend on the value imported from C during their module evaluation. The code looks something like this: // --- Module A import C from 'C' class A extends C { // ... } export {A as default} . // ---

I've been thinking around this question lot of days and i have decided to ask the experts. How browsers will handle the new import/export syntax ? I mean: will the modules be loaded asynchronously ? Referencing only my main or entry file and browsers will lazy load the requiere modules. Maybe am i missing or misunderstanding something about this new architecture ? Thank you very much! Regards. This is standardized now and supported by all major modern browsers. will the modules be loaded asynchronously? Yes, with two options available; details below. Referencing only my main or entry file and