Roque Roque - 1 year ago 206
Javascript Question

Make webpack's library output compatible with babel6

Babel's 6th version changes the functioning of

export default
and in particular its relation with commonjs

To summarise, while until babel5,
where giving the default export of the module, it now always returns the module object containing all of the exports of the module.
If one only wants the default, he must use
As explained here, there is very good reasons behind this and the aim of this question is not to break or hack this behaviour.

However, if one is building a library, he usually does not want to distribute a module but the export value of his library (e.g. a function, whatever module system is used internally).
This is well dealt with by webpack and the
configuration when using commonjs or AMD. Because prior babel's versions allowed the default export to be required with commonjs, babel was also compatible with this mechanism. However it is not the case anymore: the library now always provides an es6 module object.

Here is an example.


export default "my lib content";


var path = require("path");
var webpack = require("webpack");

module.exports = {
entry: {
lib: [ path.resolve(__dirname, "src/main.js") ],
output: {
path: path.join(__dirname, "dist"),
filename: "mylib-build.js",
library: 'myLib'
module: {
loaders: [
test: /\.js$/,
loader: "babel",
include: path.join(__dirname, "src"),
query: { presets: ['es2015'] }


<script src="dist/mylib-build.js"></script>
<!-- `myLib` will be attached to `window` -->
console.log(JSON.stringify(myLib)); // { default: "my lib content" }

This is a very simple example but I obviously want the export of mylib to be the string
"my lib content"
instead of
{ default: "my lib content" }

One solution could be to create an export source file in commonjs to perform the transformation:

module.exports = require('./main').default;

However I find this solution quite poor. One should be able to solve it at the compilation level, without changing the source code.
Any idea?

Answer Source

Was just going at this my self. Whether one like to call it a workaround or solution, there seem to be a Babel plugin that "solve it".

Using the plugin babel-plugin-add-module-exports as referenced in

Example config

var webpackOptions = {
    entry: {
        Lib1: './src/Lib1.js',
        Lib2: './src/Lib2.js'
    output: {
        filename: "Master.[name].js",
        library: ["Master","[name]"],
        libraryTarget: "var"
    module: {
        loaders: [
                loader: 'babel',
                query: {
                    presets: ['es2015'],
                    plugins: ["add-module-exports"]

This yields Master.Lib1 to be lib1 instead of Master.Lib1.default.

Recommended from our users: Dynamic Network Monitoring from WhatsUp Gold from IPSwitch. Free Download