By default, invoking a function like (function(){/*…*/})() will set the value of this in the function to window (in a browser) irrespective of whatever the value of this may be in the enclosing context where the function was created. Using call allows you to manually set the value of this to whatever you want. In … Read more
This is indeed a restriction in the AMD format. You could use exports, and that problem goes away. I find exports to be ugly, but it is how regular CommonJS modules solve the problem: define(“Employee”, [“exports”, “Company”], function(exports, Company) { function Employee(name) { this.name = name; this.company = new Company.Company(name + “‘s own company”); }; … Read more
For Babel >= 7.x ES6 code has two processing modes: “script” – When you load a file via a <script>, or any other standard ES5 way of loading a file “module” – When a file is processed as an ES6 module In Babel 7.x, files are parsed as “module” by default. The thing that is … Read more
module is a plain JavaScript object with an exports property. exports is a plain JavaScript variable that happens to be set to module.exports. At the end of your file, node.js will basically ‘return’ module.exports to the require function. A simplified way to view a JS file in Node could be this: var module = { … Read more
RequireJS implements the AMD API (source). CommonJS is a way of defining modules with the help of an exports object, that defines the module contents. Simply put, a CommonJS implementation might work like this: // someModule.js exports.doSomething = function() { return “foo”; }; //otherModule.js var someModule = require(‘someModule’); // in the vein of node exports.doSomethingElse … Read more
If you want CommonJS export behavior, you’ll need to use CommonJS directly (or use the plugin in the other answer). This behavior was removed because it caused confusion and lead to invalid ES6 semantics, which some people had relied on e.g. export default { a: ‘foo’ }; and then import {a} from ‘./foo’; which is … Read more
Even though question has been answered and accepted long ago, i just want to share my 2 cents: You can imagine that at the very beginning of your file there is something like (just for explanation): var module = new Module(…); var exports = module.exports; So whatever you do just keep in mind that module.exports … Read more