Node module is undefined when required

Question

I'm getting a very odd error when I try to require a node module. To illustrate the problem here is the code I am trying to require:

module.exports = (function(){
  this.say = function(message) {
    console.log(message);
  }
})();

Now when I require this module I get 'Cannot read property 'say' of undefined when I try to use it as follows:

var person = require('./Person.js')
person.say('Hello World!');

And yet, if I define the module as follows it works fine ...

module.exports = {
    say : function(message) {
       console.log(message);
    }
};

I even tried this notation that also worked ...

module.exports = new Person();
function Person(){
  this.say = function(message) {
    console.log(message);
  }
};

Does anyone have any idea why the first notation doesn't work properly?

Prashant Agrawal · Accepted Answer · 2016-02-07 07:31:59Z

1

The reason is your first notation doesn't return anything to export.

module.exports = (function(){
  this.say = function(message) {
    console.log(message);
  }
  return this;
})();

I guess this should solve your problem.

answered Feb 7, 2016 at 7:31

Prashant Agrawal

67010 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

ra9r Over a year ago

Wouldn't the use of (function() {...})() not return an instance of an object?

ra9r Over a year ago

Ah, no I see now what you mean. It isn't the same as invoking the new operator, but instead invokes it as a function. - Thanks!

ra9r Over a year ago

I guess I could also use the new operator as follows ... new (function(){...}). @PrashantAgrawal thanks again!

Prashant Agrawal Over a year ago

Yeah, also see this stackoverflow.com/questions/1646698/… ....It gives great description how new works.

buddy123 · Accepted Answer · 2016-02-07 07:39:38Z

0

module.exports is an object that will be returned upon require calls for that file. So assume you want write a library that does some logic, some is private, other is public. and you want to expose only your public function to other people to invoke, what your file may look like is:

// Some require calls you maybe using in your lib
function privateFunc(s) {
  console.log(s);
}

function publicFunc(s) {
  privateFunc("new log: " + s);
}

module.exports = {
  log: publicFunc
}

You later will use it as follows:

var logger= require('myLib');
logger.log("my log");

This will output:

new log: my log

Thats maybe deeper than what you actually wanted, but it is meant to understand the flow of things

answered Feb 7, 2016 at 7:39

buddy123

6,40711 gold badges50 silver badges74 bronze badges

Collectives™ on Stack Overflow

Node module is undefined when required

2 Answers 2

4 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

4 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related