Babel 6 module.exports syntax about expose-loader

[titoasty]

After a long search and testing of multiple loaders, I've found these solutions :

First solution :

Replace
export default myObject
by
module.exports = myObject

and so the expose loader works :)

Second solution :

If you don't mind about namespaces, I also found another trick :
First create a file where you import all the files you need

import Cache from './Cache';
import Loader from './Loader';

module.exports = {
    Cache,
    Loader,
};

then import this file this way :
import 'expose?Util!./utils.js';

Now Cache and Loader classes will be available globally with the namespace Util.
(you can use Util.Cache & Util.Loader everywhere).

The two solutions uses the old module.exports style, directly and indirectly.
If you find anything else, I'll be glad to hear.

Hope it will help !

[Zache]

Did you try the add-module-exports plugin for babel?

[lananelson]

@dtothefp did you find a way around this issue?

[adam-lebon]

Hi I have the same problem. I would like to export a angular module by this way:
export default angular.module('app', []);
but I have the default key which contain my angular module instead of just have my angular module :/

[qieqing]

I resolved the same problem by add-module-exports plugin, thx