The following is the code which looks int the `node_modules` folder by default

    Module.prototype.load = function(filename) {
      debug(&#39;load &#39; + JSON.stringify(filename) +
            &#39; for module &#39; + JSON.stringify(this.id));
    
      assert(!this.loaded);
      this.filename = filename;
      this.paths = Module._nodeModulePaths(path.dirname(filename));
    
      var extension = path.extname(filename) || &#39;.js&#39;;
      if (!Module._extensions[extension]) extension = &#39;.js&#39;;
      Module._extensions[extension](this, filename);
      this.loaded = true;
    };

So, following is the exact search pattern:

1. [Node.JS][1] looks to see if the given module is a core module.
    (e.g. `http`, `fs`, etc.) Always takes the precedence in the loading
    modules.

2. If the given module is not a core modules(e.g. `http`, `fs`, etc.), Node.js will then begin to search for a directory named, *`node_modules`*.

 It will start in the current directory (relative to the currently-executing file in [Node.JS][2]) and then work its way up the folder hierarchy, checking each level for a node_modules folder.
Once [Node.JS][3] finds the `node_modules` folder, it will then attempt to load the given module either as a (.js) JavaScript file or as a named sub-directory; if it finds the named sub-directory, it will then attempt to load the file in various ways. So, for example

3. If you make a request to load the module, &quot;utils&quot; and its a directory not a .js file then:&lt;br&gt;[Node.JS][4] will search a hierarchical directory for `node_modules` and `utils` in the following ways:

        ./node_modules/utils.js
        ./node_modules/utils/index.js
        ./node_modules/utils/package.json

4. If [Node.JS][5] still can&#39;t find the file in above steps, Node.js will then start to look into the directory paths from environment variables i.e. **`NODE_PATH`** set on your machine(obviously set by Node.JS installer file if you are on windows)
Not Found in all the above steps then, prints a stack trace to [stder][6]&lt;br&gt;*E.g.*: **`Error:`**`Cannot find module &#39;yourfile&#39;`
&lt;br&gt;For more information: link is [here][7] even the *cyclic require()* is explained very well..


  [1]: http://nodejs.org
  [2]: http://nodejs.org
  [3]: http://nodejs.org
  [4]: http://nodejs.org
  [5]: http://nodejs.org
  [6]: http://nodejs.org/api/stdio.html#stdio_console_error_data
  [7]: http://nodejs.org/api/modules.html#modules_modules

In fact, we can even edit the `nodevars.bat` file in which the last line is:

`if &quot;%CD%\&quot;==&quot;%~dp0&quot; cd /d &quot;%HOMEDRIVE%%HOMEPATH%&quot;` 

We can specify our own directory instead of looking after the user&#39;s home directory:

`%HOMEDRIVE%%HOMEPATH%`

so that node-modules-location will automatically looked after.

I am getting a really odd error from GCC 4.8.1 with inline functions.

I have two near-identical inline functions defined in header files (`debug.h` and `error.h`) in `src/include/`, with the only difference being what they print - one prefixes `DEBUG: ` to the message, and the other `%s: error: %s` (program name, error message). When defining the functions both inline, and compiling a debug build (so it sets the macro `DEBUG=1`), I get lots of undefined reference errors:

    src/main_debug.o
      gcc -osrc/main_debug.o src/main.c -c -Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g -DCC=&quot;\&quot;gcc\&quot;&quot; -DCFLAGS=&quot;\&quot;-Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g\&quot;&quot; -DDEBUG=1 -DBTCWATCH_VERSION=&quot;\&quot;0.0.1\&quot;&quot;
    
    src/lib/btcapi_debug.o
      gcc -osrc/lib/btcapi_debug.o src/lib/btcapi.c -c -Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g -DCC=&quot;\&quot;gcc\&quot;&quot; -DCFLAGS=&quot;\&quot;-Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g\&quot;&quot; -DDEBUG=1
    
    src/lib/libbtcapi_debug.a
      ar rc src/lib/libbtcapi_debug.a src/lib/btcapi_debug.o
      ranlib src/lib/libbtcapi_debug.a
    
    src/lib/cmdlineutils_debug.o
      gcc -o src/lib/cmdlineutils_debug.o src/lib/cmdlineutils.c -c -Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g -DCC=&quot;\&quot;gcc\&quot;&quot; -DCFLAGS=&quot;\&quot;-Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g\&quot;&quot; -DDEBUG=1
    
    src/lib/libcmdlineutils_debug.a
      ar rc src/lib/libcmdlineutils_debug.a src/lib/cmdlineutils_debug.o
      ranlib src/lib/libcmdlineutils_debug.a
    
    debug
      gcc -obtcwatch-debug src/main_debug.o -Lsrc/lib/ -lbtcapi_debug -lcmdlineutils_debug -lcurl  -ljansson 
    src/main_debug.o: In function `main&#39;:
    /home/marcoms/btcwatch/src/main.c:148: undefined reference to `debug&#39;
    src/main_debug.o:/home/marcoms/btcwatch/src/main.c:185: more undefined references to `debug&#39; follow
    collect2: error: ld returned 1 exit status
    make: *** [debug] Error 1

But changing `debug()`&#39;s definition to `static inline` removes the errors. But I have never received any errors from `error()`&#39;s definition, although its defenition is `inline`, and not `static inline`.

The definitions are all in headers (i.e. not prototyped)

undefined reference when calling inline function

Launching apps from Xcode 5 to the iOS simulator (multiple OS versions) fails with `SpringBoard failed to launch application with error: -3`. I can get around the problem by &#39;turning it off and back on again&#39; (quitting the simulator and relaunching, uninstalling and redeploying the app, etc.), but it seems to come back again later and in other projects.

Can someone help me understand what the real problem here is and if there is a permanent fix?

How to permanently fix Xcode 5 SpringBoard failed to launch application with error: -3

Is there a way to change the node_modules folder location?

For example: 

    - dir1
    - dir2
    - node_modules

to:

    - dir1
    - dir2
        - node_modules


Change node_modules location

Is there a way to change the node_modules folder location?
For example:
<pre><code class="hljs language-diff">- dir1
- dir2
- node_modules
</code></pre>
to:
<pre><code class="hljs language-markdown">- dir1
- dir2
 - node_modules
</code></pre>

As the title suggests. How do I do this? 

I want to call `whenAllDone()` after the forEach-loop has gone through each element and done some asynchronous processing.

    [1, 2, 3].forEach(
	  function(item, index, array, done) {
		 asyncFunction(item, function itemDone() {
           console.log(item + &quot; done&quot;);
           done();
         });
	  }, function allDone() {
		 console.log(&quot;All done&quot;);
         whenAllDone();
	  }
	);

Possible to get it to work like this? When the second argument to forEach is a callback function which runs once it went through all iterations?

Expected output:

    3 done
    1 done
    2 done
    All done!

Callback after all asynchronous forEach callbacks are completed

Bower enables me to specify version requirements for packages using the following syntax:

    &quot;dependencies&quot;: {
      &quot;&lt;name&gt;&quot;: &quot;&lt;version&gt;&quot;,
    },

But I have not been able to find what is the syntax to use for the `&lt;version&gt;`. I know that I can specify versions to be: 

* greater than a certain version with `&quot;&gt;1.0.0&quot;`
* greater than or equal to a version: `&quot;&gt;=1.0.0&quot;`
* or in some range: `&quot;1.0.0 - 2.0.0&quot;`. 

I also know that there is a common version syntax containing the tilde: `&quot;~1.0.0&quot;`. But I am not sure what it means and whether it is the same as `&quot;=1.0.0&quot;`.

I am also interested to know whether I am able to specify multiple non-consecutive versions, such as exactly `1.0.3` plus versions greater than `1.5.0`, etc...

What is the bower (and npm) version syntax?

I am using express to make a web app in node.js. This is a simplification of what I have:

	var express = require(&#39;express&#39;);
	var jade = require(&#39;jade&#39;);
	var http = require(&quot;http&quot;);


	var app = express();
	var server = http.createServer(app);

	app.get(&#39;/&#39;, function(req, res) {
		// Prepare the context
		res.render(&#39;home.jade&#39;, context);
	});

	app.post(&#39;/category&#39;, function(req, res) {
		// Process the data received in req.body
		res.redirect(&#39;/&#39;);
	});


My problem is the following:

If I find that the data sent in `/category` doesn&#39;t validate, I would like pass some additional context to the `/` page. How could I do this? Redirect doesn&#39;t seem to allow any kind of extra parameter.

How do I redirect in expressjs while passing some context?

What is actual difference between `res.send` and `res.json` as both seems to perform same operation of responding to client.


Difference between res.send and res.json in Express.js

Not Sure what I&#39;m doing wrong, here is my check.js

    var db = mongoose.createConnection(&#39;localhost&#39;, &#39;event-db&#39;);
    db.on(&#39;error&#39;, console.error.bind(console, &#39;connection error:&#39;));

    var a1= db.once(&#39;open&#39;,function(){
    var user = mongoose.model(&#39;users&#39;,{ 
           name:String,
           email:String,
           password:String,
           phone:Number,
          _enabled:Boolean
         });

    user.find({},{},function (err, users) {
        mongoose.connection.close();
        console.log(&quot;Username supplied&quot;+username);
        //doSomethingHere })
        });

and here is my insert.js

    var mongoose = require(&#39;mongoose&#39;);
    mongoose.connect(&#39;mongodb://localhost/event-db&#39;)

    var user = mongoose.model(&#39;users&#39;,{
         name:String,
         email:String,
         password: String,
         phone:Number,
         _enabled:Boolean
       });

    var new_user = new user({
         name:req.body.name,
         email: req.body.email,
         password: req.body.password,
         phone: req.body.phone,
         _enabled:false
       });
    
    new_user.save(function(err){
        if(err) console.log(err); 
       });

Whenever I&#39;m trying to run check.js, I&#39;m getting this error

**Cannot overwrite &#39;users&#39; model once compiled**.

I understand that this error comes due to mismatching of Schema, but I cannot see where this is happening ? I&#39;m pretty new to mongoose and nodeJS.

Here is what I&#39;m getting from the client interface of my MongoDB: 

    MongoDB shell version: 2.4.6 connecting to: test 
    &gt; use event-db 
      switched to db event-db 
    &gt; db.users.find() 
      { &quot;_id&quot; : ObjectId(&quot;52457d8718f83293205aaa95&quot;), 
        &quot;name&quot; : &quot;MyName&quot;, 
        &quot;email&quot; : &quot;myemail@me.com&quot;, 
        &quot;password&quot; : &quot;myPassword&quot;, 
        &quot;phone&quot; : 900001123, 
        &quot;_enable&quot; : true 
      } 
    &gt;

Cannot overwrite model once compiled Mongoose

When installing a node package using `sudo npm link` in the package&#39;s directory, how can I uninstall the package once I&#39;m done with development?

`npm link` installs the package as a symbolic link in the system&#39;s global package location (&#39;/usr/local/lib`). This allows you to test the package while still developing it, without having to install it over and over again.

Which npm command do I need to run to remove the link again?

How do I uninstall a package installed using npm link?



If I have a package.json file defined in my application root and run `npm install -g` it will install all the dependencies defined in package.json, globablly.

However, this doesn&#39;t seem to work in reverse.

If I do `npm uninstall -g` in my application root it throws an error, expceting me to pass it a package name.

Shouldn&#39;t this also uninstall the same packages I installed?

Am I doing something wrong?

How do you uninstall all dependencies listed in package.json (NPM)?

I&#39;ve just started using [Grunt.js][1]. It is pretty hard to set up and I am at the point of creating a `package.json` file.

Following this [tutorial][2], it says there are 3 ways to create a `package.json` file.

The first is to do `npm install grunt --save-dev`

**But what does `--save-dev` means?** I tried looking but it ends in vain.


  [1]: http://gruntjs.com/
  [2]: http://www.codingcolor.com/javascript/setting-up-a-boilerplate-gruntfile-js/

What does -save-dev mean in npm install grunt --save-dev

**I have just reinstalled Ubuntu 12.04 LTS, and before anything else i did these steps**:

1. Installed Node via package manager with the following script

        sudo apt-get update
        
        sudo apt-get install python-software-properties python g++ make
        
        sudo add-apt-repository ppa:chris-lea/node.js
        
        sudo apt-get update
        
        sudo apt-get install nodejs
        
2. Tried to install yeoman, express, n, yeoman&#39;s generators globally and all of them returned the same error

    &gt; npm ERR! Error: EACCES, symlink &#39;../lib/node_modules/n/bin/n&#39;
    
    &gt; npm ERR!  { [Error: EACCES, symlink &#39;../lib/node_modules/n/bin/n&#39;] errno: 3, code: &#39;EACCES&#39;, path: &#39;../lib/node_modules/n/bin/n&#39; }
    
    &gt; npm ERR! 
    
    &gt; npm ERR! Please try running this command again as root/Administrator.
    
    &gt; npm ERR! System Linux 3.8.0-29-generic
    
    &gt; npm ERR! command &quot;/usr/bin/node&quot; &quot;/usr/bin/npm&quot; &quot;install&quot; &quot;-g&quot; &quot;-d&quot; &quot;n&quot;
    
    &gt; npm ERR! cwd /home/heberlz
    
    &gt; npm ERR! node -v v0.10.20
    
    &gt; npm ERR! npm -v 1.3.11
    
    &gt; npm ERR! path ../lib/node_modules/n/bin/n
    
    &gt; npm ERR! code EACCES
    
    &gt; npm ERR! errno 3
    
    &gt; npm ERR! stack Error: EACCES, symlink &#39;../lib/node_modules/n/bin/n&#39;
    
    &gt; npm ERR! 
    
    &gt; npm ERR! Additional logging details can be found in:
    
    &gt; npm ERR!     /home/heberlz/npm-debug.log
    
    &gt; npm ERR! not ok code 0

3. **Reclaimed ownership of the following folders recursively** ~/.npm, /usr/lib/node, /usr/lib/node_modules, and of the following symlinks /usr/bin/node, /usr/bin/nodejs **with absolutely no success**

I need to install yeoman and its generators without sudo not to be in trouble later on :(

NPM modules won&#39;t install globally without sudo

After `npm init` I can add dependencies in my package.json using this:
    
    npm install package --save

And say, I want to `uninstall` the package and I do so by doing:

    npm uninstall package

but I want my package.json to be updated accordingly too without me having to manually go to the file and delete that line. 

From the npm docs it says: 

&gt; It is strictly additive, so it does not delete options from your package.json without a really good reason to do so.

So, I just wanted to know if this is even possible. 

Content Type	Original Author	Original Content on Stackoverflow
Question	M K	View Question on Stackoverflow
Solution 1 - node.js	Amol M Kulkarni	View Answer on Stackoverflow
Solution 2 - node.js	mohu	View Answer on Stackoverflow

Change node_modules location

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Solution 2 - node.js

How to permanently fix Xcode 5 SpringBoard failed to launch application with error: -3

undefined reference when calling inline function

Attributions