node package manager
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »

es6-translate

es6-translate Build Status

Load commonjs modules in an es6 enviroment, it always returns a default export.

Overly convoluted example

lib1.js

'use strict';
var foo = require('./lib2');
 
module.exports = function () {
  return foo.bar;
};

lib2.js

exports.bar = 'baz';

index.js

var es6Translate = require('es6-translate');
var System = require('es6-module-loader').System;
System.instantiate = es6Translate.instantiate;
System.import('lib1').then(function(m) {
  console.log(m.default());
});

from the console

node index.js # prints baz

there is also a patch method that also updates System.import to always return the default value (because that's all that's ever exported) and in node fixes the path resolution.

var es6Translate = require('es6-translate');
var System = require('es6-module-loader').System;
es6Translate.patch(System);
System.import('lib1').then(function(m) {
  console.log(m());
});

or if you don't want to mess with global System object pass in Loader too

var es6Translate = require('es6-translate');
var es6ModuleLoader = require('es6-module-loader');
var Sys = es6Translate.patch(es6ModuleLoader.System, es6ModuleLoader.Loader);
Sys.import('lib1').then(function(m) {
  console.log(m());
});

Inside CommonJS modules, if there is a key named default in a module it is assumed to be the default export and just that is imported, to avoid this behavior pass a truthy second argument to require, ex

//export.js 
var val;
exports.default = 9;
exports.get = function () {
    if (typeof val !== 'undefined') {
        return val;
    }
    return this.default;
}
exports.set = function (nval) {
    val = nval;
}
 
//import.js 
var mod = require('./export');
// mod === 9; 
var mod = require('./export', true);
// does what you want it to do.