If module.exports is assigned an object, either by a variable name or an object literal, does it have access to variables defined outside of module.exports within the same file?

FAQ JavaScript FAQ
#1

Question

If module.exports is assigned an object, either by a variable name or an object literal, does it have access to variables defined outside of module.exports within the same file?

Answer

The object being assigned to module.exports will have access to other variables that are defined within the same scope, however if those other variables are not also being exported, we will not have access to them in the file importing the module.

For example:
moduleToExport.js:

const myVar = {
  prop1: 'prop 1'
}

const objToExport = {
  key1: myVar.prop1
}

module.exports = objToExport;

main.js:

const myModule = require('./moduleToExport.js'); //require the exported module which is the objToExport object

console.log(myModule); //logs the object `{ key1: 'prop 1' }` to the console, which does not include a reference to the variable myVar
13 Likes
#3

Hello,

Could you please give me an explanation about the declaration on the section INTERMEDIATE JAVASCRIPT MODULES >> 4. module.exports II:

You are asking for a declaration of an module export + anonymous function and I did this:

module.exports = {
  myAirplane: "CloudJet",
  displayAirplane: () => {
    return module.exports.myAirplane
  }
};

But I saw that you are using return this.myAirplane instead of return module.exports.myAirplane what would be the best practice or should I avoid the use of fat arrows functions and instead I have to use displayAirplane: function() {...;}?

Thanks in advance for your patience.

2 Likes
#4

I believe it’s just programmer preference. You are trading typing () => instead of function() for having to type module.exports instead of this. Both work, so do what you prefer.

4 Likes
#5

Great! thanks I’ll keep in mind.

1 Like
#6

Or as the shortest and most concise alternative, you could also just use the ES6 syntax and write

displayAirplane() {
   return this.myAirplane;
}
5 Likes
#7

Or this…

displayAirplane: () => this.myAirplane
3 Likes
#8

I tried this way, but then the following happens:
console.log(Airplane); // will print { myAirplane: ‘CloudJet’,
// displayAirplane: [Function: displayAirplane] }
console.log(Airplane…displayAirplane()); // will print javascript_modules-airplanes/2-
// airplane.js:6 return undefined.myAirplane;

1 Like
#9

yes, it is because, Arrow functions are anonymous and change the way this binds in functions.

2 Likes
#10

I am a bit confused. When it logs '{ key1: ‘prop 1’ }` where does ‘prop 1’ come from if it is not referencing the myVar object?

2 Likes
#11

Understand this, you are using arrow function thus you can not use this keyword though, because in normal function this refers to the local object itself but in case of Arrow function they don’t have their own this context.It will refers to the global object.,which dose not have same property a object,thus returned undefined.

3 Likes
#12

Yes, Even the chapter says the same:

https://www.codecademy.com/courses/introduction-to-javascript/lessons/advanced-objects/exercises/arrow-and-this

  • The key takeaway from the example above is to avoid using arrow functions when using this in a method!
1 Like
#13

All these different ways to do the same thing confuses the heck out of me, especially because not all of them work in every scenario.

3 Likes
#14

So… we can ses as below

if this is true… then .

Or as the shortest and most concise alternative, you could also just use the ES6 syntax and write

displayAirplane() {
   return this.myAirplane;
}

these mentions are true… but

what @remysmith says like

this is a syntax error right?

since arrow function will not have it’s own this.
here maybe console will throw an error

is it correct understanding?’
thank you for working together everyone ! :smile: :star_struck: