es6-modules

i have an index.js file that reads: import aReducer from './ducks/a'; import bReducer from './ducks/b'; import * as aSelectors from './ducks/a'; import * as bSelectors from './ducks/b'; console.log(aReducer) //function i expect console.log(aSelectors) //object with keys to selectors i expect export { aReducer, bReducer, ...aSelectors, ...bSelectors }; If I console.log in this file I see that the reducers are functions I expect and the selectors alias are objects with keys to the selectors I expect. The reducers are default exports for the duck files and the selectors are exports from the same

Is it possible to use es6 module system and import modules in web browsers? With chrome 61, es6 module system is introduced to the world of web browsers. This link https://developers.google.com/web/fundamentals/primers/modules can be referred for more details on how chrome implements the module system. Some of the important features of es6 module system discussed in the above link are: Modules by default are strict mode. They are not lexical top-level scope, which is var foo = 42 in module file won't be available as window.foo. Modules are included in html file as <script type="module" src=

I have some components in my vue project. I don't like import loader from '@/components/someComponent1/someComponent1.vue'; because it's a lot to write and I have to repeat it for every component. So I wrote an index.js for the components folder: export { default as someComponent1 } from './someComponent1/someComponent1.vue'; export { default as someComponent2 } from './someComponent2/someComponent2.vue'; ... This will allow me to import multiple components in one line: import { someComponent1, someComponent2 } from '@/components'; My question: Is it possible that the index.js -ish-way is

I want my users to be able to use JavaScript as a scripting language inside my JavaScript application. In order to do so, I need to dynamically execute the source code. There seem to be two main options for dynamically executing JavaScript: a) Use eval(...) method ( or var func = new Function(...); ) . b) Add a <script> node to the DOM (for example by using $('body').append(...) ). Both methods work fine as long as I do not use any import statements in the dynamically executed source code. If I include import statements I get the error message Unexpected identifier . Example user source code

In this question that I asked here: Why does mutating a module update the reference if calling that module from another module, but not if calling from itself? I'm asking about the nature of module mutation. However as it it turns out, ES6 modules can't actually be mutated - all of their properties are treated as constants. ( See this answer ) But somehow - when Jest tests modules - they can be mutated, and that's how Jest allows for mocking. How is this happening? I imagine that it's a babel plugin that that's running - transpiling the module to CommonJS modules? Is there any documentation