On Sat, Apr 19, 2014 at 01:19:36AM +0200, Kevin Ingwersen wrote: > Hey! > > Oh yes, you got that one right. In my cases, I just have a folder containing > my stuff, or app. Let's take an example, for a WebSockets server... > > ChatSock > |- main.js > |- lib/other.js > |- node_modules > |- socket.io > |- someOtherStuff > > the node_modules within your app/project directory is the "local npm install > path". So in your case, if I wanted to add Karma, I would navigate right into > that folder, and > > $ npm install karma > > And it would appear next to socket.io and someOtherStuff.
Yep! One addition. It's probably smart to make a list of those dependencies. Make a package.json! npm init # makes a package.json. npm install --save socket.io someOtherStuff # Installs those things and saves 'em in package.json. ChatSock |- package.json |- main.js |- lib/other.js |- node_modules |- socket.io |- someOtherStuff
pgpc6fof22GdI.pgp
Description: PGP signature
