es6-module-loader

From this article : https://hacks.mozilla.org/2015/08/es6-in-depth-modules/ It is written that The new standard is designed to interoperate with existing CommonJS and AMD modules. And more precisely All CommonJS and AMD modules are presented to ES6 as having a default export If it is really the case all we'd need is a ES6 polyfill and we wouldn't have to do use anything else. Yet for eg this ES6 Polyfill : https://github.com/ModuleLoader/es6-module-loader doesn't seem to allow loading CommonJS/AMD modules from ES6 but only solutions built on top of it like SystemJS allow it. So the question is

Let's say I have a simple class like this in fileA.js : class foo { constructor(x) { this.name = x } fooMethod(x) { return x + 'hello'; } } And I want to import and use fooMethod in fileB.js like this: import { fooMethod } from './fileA'; class bar() { ... barMethod(x) { return fooMethod(x); } } How would I write the export in fileA to achieve this? You would have to export it on the prototype. But remember that if you do that you won't call the function in the class/object context: export foo.prototype. fooMethod However I would recommend you to not to do so. Okay, due to your comment you

i am making VideoPlayer react component with jwpalyer and i am using webpack es6 for loading module webpack support npm module loading & there is no npm for jwplayer so am trying to include jwplayer.js using es6 import but it giving me error ReferenceError: window is not defined so any one can help me to properly setup jwplayer with webpack import React, { PropTypes, Component } from 'react'; import $ from 'jquery'; import Player from "./lib/jwplayer/jwplayer.js"; import styles from './VideoPayer.css'; import withStyles from '../../decorators/withStyles'; import Link from '../Link';

There is no detalied explanation of what exactly es6 import and export do under the hood. Someone describe import as an read only view. Check the code below: // lib/counter.js export let counter = 1; export function increment() { counter++; } export function decrement() { counter--; } // src/main.js import * as counter from '../../counter'; console.log(counter.counter); // 1 counter.increment(); console..log(counter.counter); // 2 My question is if two modules import the same counter module and the first module increment the counter, will the second module also see the the counter as

Looking on the internet I'm confused with the special "index.js" module file. Using babelJS + nodeJS or Browserify/Webpack I can import an "index.js" module inside a "libs" directory using import myLib from "./libs" (ie. omitting the /index or /index.js part). Is the "index.js" module resolution (specifying the containing folder) supported by the ES6 (EcmaScript 2015) modules official standard? Or is it just "custom" NodeJS/CommonJS transpiling behaviour? Will it be possible to omit the /index | /index.js part of the import in all browsers as well (when modules will be supported on all

In ES2015, it's possible to import an entire module as an object whose properties are the module's exports: import * as name from 'module'; I find this to be extraordinarily useful for namespacing and use it all the time. It's also possible to re-export other modules' exports: export { name } from 'module'; // selectively export * from 'other-module'; // indiscriminately Now I'm trying to write a library with namespacing in this style. The intuitive way of collecting everything in the top-level module would be like this: export * as name from 'module'; But that doesn't seem to work; Babel and