* Fix buildExportAll to account for commonjs/amd If the re-exported module was generated with Babel and it is a commonjs or amd module and so is the current module, this will result in an attempt to redefine the __esModule property, which throws a runtime error. * Add test: don't overwrite __esModule on re-export (Failing.) * fixup tests * Add fix for systemjs
babel-plugin-transform-es2015-modules-umd
Installation
$ npm install babel-plugin-transform-es2015-modules-umd
Usage
Via .babelrc (Recommended)
.babelrc
{
"plugins": ["transform-es2015-modules-umd"]
}
You can also override the names of particular libraries when this module is
running in the browser. For example the es6-promise library exposes itself
as global.Promise rather than global.es6Promise. This can be accomidated by:
{
"plugins": [
["transform-es2015-modules-umd", {
"globals": {
"es6-promise": "Promise"
}
}]
]
}
Via CLI
$ babel --plugins transform-es2015-modules-umd script.js
Via Node API
require("babel-core").transform("code", {
plugins: ["transform-es2015-modules-umd"]
});