Node.js - cannot find module

Question

I'm using Node Boilerplate and it all worked fine until I decided create another project on top of it (in another dir).

Now I have exactly the same code base (this project AS IS) in two different folders. I can run one of it without any problems but another one is failing with:

% node app.js
node.js:116
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
Error: Cannot find module 'connect/middleware/router'
    at Function._resolveFilename (module.js:299:11)
    at Function._load (module.js:245:25)
    at require (module.js:327:19)
    at Object.<anonymous> (/home/gotts/Sites/nodejs-uploadr/lib/express/lib/express/server.js:17:14)
    at Module._compile (module.js:383:26)
    at Object..js (module.js:389:10)
    at Module.load (module.js:315:31)
    at Function._load (module.js:276:12)
    at require (module.js:327:19)
    at Object.<anonymous> (/home/gotts/Sites/nodejs-uploadr/lib/express/lib/express/index.js:28:31)

There is a similar problem explained here - https://github.com/visionmedia/express/issues/535 which says that the problem is in the incompatible version of connect/express.

But how is this possible? The source code is exactly the same in two folders and it works fine in one copy and fails in another?

Ricardo Tomasi · Accepted Answer · 2011-03-14 04:14:08Z

8

Do the two folders share a common parent? Node looks for modules in ~/.node_modules and /node_modules in your app dir.

answered Mar 14, 2011 at 4:14

Ricardo Tomasi

35.3k2 gold badges58 silver badges66 bronze badges

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

Comments

user80805 · Accepted Answer · 2011-03-14 12:35:10Z

7

OK, let me answer my own question:

Sorry for misinformation - those two folders were not exactly the same(I'm gonna need to learn unix diff better). And there it require("connect") in code

Local checkout of connect into /lib folder takes precedence but if it's not there - connect will be loaded from the ~/.node_modules as Ricardo previously set.

answered Mar 14, 2011 at 12:35

user80805

6,5685 gold badges30 silver badges31 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 11:45:33Z

5

@see node.js express module not loading properly in the last comment, maybe it helps

the basic idea behind it is to install the module inside your application folder, not on a system level

edited May 23, 2017 at 11:45

CommunityBot

11 silver badge

answered May 21, 2011 at 12:52

Georgiana

3231 gold badge4 silver badges9 bronze badges

1 Comment

Adam Over a year ago

This works for me, but I'm confused as to why installing system level with -g doesn't find the module in the js file being run.

Collectives™ on Stack Overflow

Node.js - cannot find module

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related