To use export default with Babel, you can do 1 of the following: require(“myStuff”).default npm install babel-plugin-add-module-exports –save-dev Or 3: //myStuff.js var thingToExport = {}; Object.defineProperty(exports, “__esModule”, { value: true }); exports[“default”] = thingToExport;
CommonJS modules allow two ways to define exported properties. In either case you are returning an Object/Function. Because functions are first class citizens in JavaScript they to can act just like Objects (technically they are Objects). That said your question about using the new keywords has a simple answer: Yes. I’ll illustrate… Module exports You … Read more
Use var instead of import. var json = require(‘./calls.json’); You’re loading a JSON file, not a module, so import shouldn’t be used is this case. When var is used, require() is treated like a normal function again. If you’re using a Node.js definition, everything should just work, otherwise require will need to be defined.
According to the Webpack documentation, you can use the externals property on the config object “to specify dependencies for your library that are not resolved by webpack, but become dependencies of the output. This means they are imported from the enviroment while runtime [sic].” The example on that page illustrates it really well, using jQuery. … Read more
When the D module is executed, the console will print this message: A evaluated A constructor Which means that the A module was evaluated only once, even if it was imported multiple times by other modules. The evaluation rules for ES6 modules is the same as for commonjs format: A module is a piece of … Read more
Well there’s no reliable way to detect running in Node.js since every website could easily declare the same variables, yet, since there’s no window object in Node.js by default you can go the other way around and check whether you’re running inside a Browser. This is what I use for libs that should work both … Read more
Unfortunately import statements does not work like object destructuring. Curly braces here mean that you want to import token with this name but not property of default export. Look at this pairs of import/export: //module.js export default ‘A’; export var B = ‘B’; //script.js import A from ‘./a.js’; //import value on default export import {B} … Read more
Update If you use Typescript 2^ just use the following command: npm i @types/node –save-dev (instead of –save-dev you can just use shortcut -D) or install it globally: npm i @types/node –global You can also specify typeRoots or types in your tsconfig.json if you want but by default all visible “@types” packages are included in … Read more
Yes, and I owe this answer to ded and his awesome modules: (function(name, definition) { if (typeof module != ‘undefined’) module.exports = definition(); else if (typeof define == ‘function’ && typeof define.amd == ‘object’) define(definition); else this[name] = definition(); }(‘mod’, function() { //This is the code you would normally have inside define() or add to … Read more
The AMD proposal allows you to just return a value for the exported object. But note that is a feature of the AMD proposal, it is just an API proposal, and will make it harder to translate the module back to a regular CommonJS module. I think that is OK, but useful info to know. … Read more