#MY WEBROOT INSTALL#

This generally considered bad practice as different projects may depend on different versions of the same module.

#MY WEBROOT INSTALL#

It is possible to install modules globally with npm using the g-flag: npm install -g express. Are there any major risks with having modules in a webroot?Īssuming that you by 'webroot' mean in the root of the server or any folder outside of your project: yes. Is it possible to have modules in a folder outside of the projectĢ.

What do you guys do, what is best practice for production apps? May I have some examples of your production practices and why.ġ.

Are there any major risks with me having my libs in a webroot or have I missed something fundamental here with the way Node works.

Is what I'm asking even possible, if so then how?.

Var express=require('./express') which doesn't work either giving me the 'Cannot Find module' type error. Then it all goes wobbly and Node's require() magic breaks. If I setup the project as follows: /my_project Call me old fashioned but that's how I'm used to doing stuff in the PHP and C# world. I'm just so used to keeping the bare minimum in my publicly exposed webroot and don't feel right with the libs being in there. I was wondering if there was any way I could have the /node_modules dir outside of my webroot and not break my application. I've setup my simple expressJS based Node project as follows: /my_project I was trying to move my node_modules (libraries) directory outside of the public 'webroot' and need advice and guidance. I'm new to Node but am enjoying myself so far.

My webroot