To use export default with Babel, you can do 1 of the following: require(“myStuff”).default npm install babel-plugin-add-module-exports –save-dev Or 3: //myStuff.js var thingToExport = {}; Object.defineProperty(exports, “__esModule”, { value: true }); exports[“default”] = thingToExport;
Yes, there is. In fact, Webstorm can’t automatically parse and apply Webpack config, but you can set up aliases the same way. You just have to mark the parent folder of “utils” (in your example) as a resource root (right-click, mark directory as / resource root). We just managed to do with the following structure … Read more
The answer is to use “init functions”. For reference, look at the two messages starting here: https://esdiscuss.org/topic/how-to-solve-this-basic-es6-module-circular-dependency-problem#content-21 The solution looks like this: // — Module A import C, {initC} from ‘./c’; initC(); console.log(‘Module A’, C) class A extends C { // … } export {A as default} – // — Module B import C, {initC} … Read more
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 browsers will lazy load the requiere modules. Not so much “lazy,” but yes. Enabling it Details in the spec here and here (and … Read more
JavaScript modules are evaluated asynchronously. However, all imports are evaluated prior to the body of module doing the importing. This makes JavaScript modules different from CommonJS modules in Node or <script> tags without the async attribute. JavaScript modules are closer to the AMD spec when it comes to how they are loaded. For more detail, … Read more
2018 Update: The module loader spec is now a part of the ES Spec – what you are describing is allowed and possible with <script type=”module”> in browsers and with a custom –loader with Node.js as well as with Deno if you’re into that. The module loader spec and the import/export syntax are separate. So … Read more
It’s supported in: Safari 10.1 Chrome 61 Firefox 54 – behind the dom.moduleScripts.enabled setting in about:config. Edge 16
You need to install the es2015 preset: npm install babel-preset-es2015 and then configure babel-loader: { test: /\.jsx?$/, loader: ‘babel-loader’, exclude: /node_modules/, query: { presets: [‘es2015’] } }
Here is how to do this as of Typescript 2.0: (tsd and typings are being deprecated in favor of the following): $ npm install –save lodash # This is the new bit here: $ npm install –save-dev @types/lodash Then, in your .ts file: Either: import * as _ from “lodash”; Or (as suggested by @Naitik): … Read more