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
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.
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
Turned out to be an issue with Webpack just not resolving an import – talk about horrible horrible error messages 🙁 // I Had to change: import DoISuportIt from ‘components/DoISuportIt’; // to (notice the missing `./`) import DoISuportIt from ‘./components/DoISuportIt’;
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
I have used RequireJS extensively in the past (implementation on BBC iPlayer in 2010) and it works well. It can handle CommonJS modules, but it needs an additional wrapper, which I find annoying. If you want to use those modules in Node.js as well, you need to use RequireJS on the server side as well, … Read more
Would there be a new instance every time I import A? No, modules are only evaluated once. Is one of the benefits of B the ability to use object destructuring and then use method1 as if it existed locally? Yes, though it’s not called “destructuring”. They’re named imports (or named exports of the module), and … 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
Here’s what I think is the ‘rightest’ answer for this situation. Say you have a script file called quadtree.js. You should build a custom node_module that has this sort of directory structure… ./node_modules/quadtree/quadtree-lib/ ./node_modules/quadtree/quadtree-lib/quadtree.js ./node_modules/quadtree/quadtree-lib/README ./node_modules/quadtree/quadtree-lib/some-other-crap.js ./node_modules/quadtree/index.js Everything in your ./node_modules/quadtree/quadtree-lib/ directory are files from your 3rd party library. Then your ./node_modules/quadtree/index.js file will just … 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