It&#39;s not possible to disable only `postinstall` scripts. However, you can disable all scripts using:

    $ npm install --ignore-scripts

As delbertooo mentionned in the comments, this also disables the scripts of the dependencies.

You can also enable the settings in npm configuration file.

`npm config set ignore-scripts true`

Note: This will disable scripts for all NPM packages.

I wanted to disable postinstall script for my project but wanted all scripts of my project&#39;s dependencies to run when I do `npm install`.
This is what I ended up doing.

 1. Create a script `./scripts/skip.js` 

```js
if (process.env.SKIP_BUILD) {
    process.exit(0);
} else {
    process.exit(1);
}
```
2. In your package.json file 
```json
 &quot;scripts&quot;: {
  ...
  &quot;postinstall&quot;: &quot;node ./scripts/skip.js || npm run build&quot;,
  ...
 }
```
now just set the environment variable SKIP_BUILD=1 to prevent your package from building and your dependencies will build just fine 

```
SKIP_BUILD=1 npm install
```


To do this for your own library, I recommend something simple like:


 
    #!/usr/bin/env bash

    ## this is your postinstall.sh script:

    set -e;
    
    if [ &quot;$your_pkg_skip_postinstall&quot; == &quot;yes&quot; ]; then
      echo &quot;skipping your package&#39;s postinstall routine.&quot;;
      exit 0;
    fi

then do your npm install with:

    your_pkg_skip_postinstall=&quot;yes&quot; npm install

If you&#39;re using NPM&gt;=7, you can also remove the `postinstall` script temporarily:

```bash
npm set-script postinstall &quot;&quot;
npm install
```

Source:
https://docs.npmjs.com/cli/v7/commands/npm-set-script/

In [YAML](http://yaml.org/spec), you can easily create [multi-line strings](https://stackoverflow.com/questions/3790454/in-yaml-how-do-i-break-a-string-over-multiple-lines). However, I would like the ability to create a multi-line array (mainly for readibility within config files) using the `|` character.

A YAML **array** can be represented as: `[&#39;key1&#39;, &#39;key2&#39;, &#39;key3&#39;]`.

A YAML **sequence** uses a dash followed by a space and then a string:

    - String1
    - String2
    - String3

This would evaluate to: `[&#39;string1&#39;, &#39;string2&#39;, &#39;string3&#39;]`.

A YAML **mapping** is an array of key and value pairs that we see all the time in YAML:

    Key1: string1
    Key2: string2
    Key3: string3

This is all well and good, but I can&#39;t for the life of me see how to do a multi-line array. Something like this:

    |
    [&#39;string1&#39;, &#39;string2&#39;, &#39;string3&#39;]
    [&#39;string4&#39;, &#39;string5&#39;, &#39;string6&#39;]

Short of creating multiple array mappings in YAML and merging them in my programming language of choice, is there any way to achieve multi-line arrays, maybe with `{ }` like Python has but in YAML?

YAML Multi-Line Arrays

I am trying to use Bootstrap to make an interface for a program. I added jQuery 1.11.0 to the `&lt;head&gt;` tag and thought that was that, but when I launch the web page in a browser jQuery reports an error:

&lt;!-- language: lang-none --&gt;

    Uncaught Error: Bootstrap&#39;s JavaScript requires jQuery

I have tried using jQuery 1.9.0, I have tried with copies hosted on several CDNs, but I can&#39;t get it work. Can anybody point out what I&#39;m doing wrong?


Bootstrap throws Uncaught Error: Bootstrap&#39;s JavaScript requires jQuery

Is it any npm option exist to disable postinstall script while installing package? Or for rewriting any field from package.json?

npm: disable postinstall script for package

<p>Is it any npm option exist to disable postinstall script while installing package? Or for rewriting any field from package.json?</p>


How to configure my shell so that `nvm use` run automatically every time there&#39;s a .nvmrc file on the directory and use the latest version or a global config when there&#39;s no .nvmrc file?

run `nvm use` automatically every time there&#39;s a .nvmrc file on the directory

I&#39;m a new user to gulp.js.  I&#39;d like to move all of my non-javascript files to a build directory.  What I&#39;ve got right now is this:

    //Test copy
    gulp.task(&#39;test-copy&#39;, function() {
    	gulp.src([&#39;myProject/src/**/*.!(js|map|src)&#39;])
    		.pipe(gulp.dest(&#39;myProject/build&#39;));
    });


    //Results for various files
    myProject/css/style.css //Copied - GOOD
    myProject/html/index.html //Copied - GOOD
    myProject/js/foo.js //Not Copied - GOOD
    myProject/js/bar.min.js //Copied - BAD!
    myProject/js/jquery-2.0.3.min.js //Copied - BAD!
    myProject/js/jquery-2.0.3.min.map //Copied - BAD!

As you can see, it only matches after the first dot in the file path string, not the last one, as I&#39;d like.  How can I modify the glob search string to behave as I&#39;d like?

Glob matching, exclude all JS files

I am new with ```Express```. As ```Express 4.x``` has removed bundled middlewares.
Any middleware I want to use should be required. When I read the README with [express-session][1] and [cookie-session][2] on github, I feel it hard to understand the difference.

So I try to write simple code to figure it out. I run twice for each middleware.

    var express = require(&#39;express&#39;)
	  , cookieParser = require(&#39;cookie-parser&#39;)
	  , session = require(&#39;cookie-session&#39;)
	  , express_sess = require(&#39;express-session&#39;)
	  , app = express();

	app.use(cookieParser())
	app.use(session({ keys: [&#39;abc&#39;], name: &#39;user&#39; }));
	//app.use(express_sess({ secret: &#39;abc&#39;, key: &#39;user&#39;}));
	app.get(&#39;/&#39;, function (req, res, next) {
		res.end(JSON.stringify(req.cookies));
		console.log(req.session)
		console.log(req.cookies)
	});

	app.listen(3000);

For ```cookie-session```, I always get {} in my terminal.

For ```express-session```, I get things like this.

    req.session: { cookie: { 
         path: &#39;/&#39;,
         _expires: null,
         originalMaxAge: null,
         httpOnly: true 
       } 
    }

    req.cookie: {user: &#39;s:aJ97vKA5CCwxqdTj0AV1siRQ.fWusS5+qfCKICtwkfrzcZ/Gq8P0Qdx/kx8mTBhoOhGU&#39;}

It really confuses me. So how to explain the result with the basic use? And what&#39;s the difference between them? When should I use them? 



  [1]: https://github.com/expressjs/session
  [2]: https://github.com/expressjs/cookie-session

What&#39;s difference with express-session and cookie-session?

I am trying to update a value in the nested array but can&#39;t get it to work.

My object is like this

     {
        &quot;_id&quot;: {
            &quot;$oid&quot;: &quot;1&quot;
        },
        &quot;array1&quot;: [
            {
                &quot;_id&quot;: &quot;12&quot;,
                &quot;array2&quot;: [
                      {
                          &quot;_id&quot;: &quot;123&quot;,
                          &quot;answeredBy&quot;: [],   // need to push &quot;success&quot; 
                      },
                      {
                          &quot;_id&quot;: &quot;124&quot;,
                          &quot;answeredBy&quot;: [],
                      }
                 ],
             }
         ]
     }

I need to push a value to &quot;answeredBy&quot; array.

In the below example, I tried pushing &quot;success&quot; string to the &quot;answeredBy&quot; array of the &quot;123 _id&quot; object but it does not work.


    callback = function(err,value){
         if(err){
             res.send(err);
         }else{
             res.send(value);
         }
    };
    conditions = {
        &quot;_id&quot;: 1,
        &quot;array1._id&quot;: 12,
        &quot;array2._id&quot;: 123
      };
    updates = {
       $push: {
         &quot;array2.$.answeredBy&quot;: &quot;success&quot;
       }
    };
    options = {
      upsert: true
    };
    Model.update(conditions, updates, options, callback);

I found this [link][1], but its answer only says I should use object like structure instead of array&#39;s. This cannot be applied in my situation.  I really need my object to be nested in arrays 

It would be great if you can help me out here. I&#39;ve been spending hours to figure this out.

Thank you in advance!

  [1]: https://stackoverflow.com/questions/4121666/updating-nested-arrays-in-mongodb

Updating a Nested Array with MongoDB

I am working through setting up a http server using node.js and engine. However, I keep running into issues that I have little information on how to resolve I would appreciate some help solving  this please. 

    Error: No default engine was specified and no extension was provided. 
    at new View (...\node_modules\express\lib\view.js:41:42) 
    at Function.app.render (...\node_modules\express\lib\application.js:484:12) 
    at ServerResponse.res.render (...\node_modules\express\lib\response.js:783:7) 
    at Layer.handle (...\app.js:123:7) 
    at trim_prefix (...\node_modules\express\lib\router\index.js:225:17) 
    at c (...\node_modules\express\lib\router\index.js:198:9) 
    at Function.proto.process_params (...\node_modules\express\lib\router\index.js:253:12) 
    at next (...\node_modules\express\lib\router\index.js:189:19) 
    at next (...\node_modules\express\lib\router\index.js:202:7) 
    at next (...\node_modules\express\lib\router\index.js:166:38)



Below is what I have set up to start up this engine. 


    var http = require(&#39;http&#39;);  
    var module = require(&quot;module&quot;)
    var logger = require(&#39;morgan&#39;);
    var express = require(&#39;express&#39;);
    var app =  module.exports = express();
    var silent = &#39;test&#39; == process.env.NODE_ENV;
    var httpServer = http.createServer(app);  // app middleware
    
    app.enable(&#39;strict routing&#39;);
    // app.all(&#39;*&#39;, function(req, res, next)/*** CORS support.*/
    // {
    //   if (!req.get(&#39;Origin&#39;)) return next();// use &quot;*&quot; here to accept any origin
    //   res.set(&#39;Access-Control-Allow-Origin&#39;, &#39;http://localhost:3000&#39;);
    //   res.set(&#39;Access-Control-Allow-Methods&#39;, &#39;GET, POST&#39;);
    //   res.set(&#39;Access-Control-Allow-Headers&#39;, &#39;X-Requested-With, Content-Type&#39;);
    //   res.set(&#39;Access-Control-Allow-Max-Age&#39;, 3600);
    //   if (&#39;OPTIONS&#39; == req.method) return res.send(200);
    //   next();
    // });
    app.set(&#39;views&#39;, __dirname + &#39;/views&#39;); // general config
    app.set(&#39;view engine&#39;, &#39;html&#39;);
    app.get(&#39;/404&#39;, function(req, res, next){
    next();// trigger a 404 since no other middleware will match /404 after this one, and we&#39;re not responding here
    });
    app.get(&#39;/403&#39;, function(req, res, next){// trigger a 403 error
      var err = new Error(&#39;not allowed!&#39;);
      err.status = 403;
      next(err);
    });
    app.get(&#39;/500&#39;, function(req, res, next){// trigger a generic (500) error
      next(new Error(&#39;keyboard cat!&#39;));
    });
    app.use(express.static(__dirname + &#39;/public&#39;)); 
    //error handlers
    app.use(logErrors);
    app.use(clientErrorHandler);
    app.use(errorHandler);  
    // middleware with an arity of 4 are considered error handling middleware. When you next(err)
    // it will be passed through the defined middleware in order, but ONLY those with an arity of 4, ignoring regular middleware.
    function clientErrorHandler(err, req, res, next) {
      if (req.xhr) {// whatever you want here, feel free to populate properties on `err` to treat it differently in here.
      res.send(err.status || 500, { error: err.message });
      } 
      else 
      { next(err);}
    };
    // create an error with .status. we can then use the property in our custom error handler (Connect repects this prop as well)
    function error  (status, msg) {
      var err = new Error(msg);
      err.status = status;
      return err;
    };
    function logErrors  (err, req, res, next) {
      console.error(err.stack);
      next(err);
    };
    function errorHandler (err, req, res, next) {
      res.status(500);
      res.render(&#39;error&#39;, { error: err });
    };
    
    // Error handlers
    // Since this is the last non-error-handling middleware use()d, we assume 404, as nothing else responded.
    // $ curl http://localhost:3000/notfound
    // $ curl http://localhost:3000/notfound -H &quot;Accept: application/json&quot;
    // $ curl http://localhost:3000/notfound -H &quot;Accept: text/plain&quot;
    app.use(function(req, res, next){
      res.status(404); 
      if (req.accepts(&#39;html&#39;)) {// respond with html page
        res.render(&#39;404&#39;, { url: req.url });
        return;
      } 
      if (req.accepts(&#39;json&#39;)) {// respond with json
        res.send({ error: &#39;Not found&#39; });
        return;
      } 
      res.type(&#39;txt&#39;).send(&#39;Not found&#39;);// default to plain-text. send()
    });
    
    // error-handling middleware, take the same form as regular middleware, however they require an
    // arity of 4, aka the signature (err, req, res, next).when connect has an error, it will invoke ONLY error-handling middleware.
    
    // If we were to next() here any remaining non-error-handling middleware would then be executed, or if we next(err) to
    // continue passing the error, only error-handling middleware would remain being executed, however here
    // we simply respond with an error page.
    app.use(function(err, req, res, next){
      // we may use properties of the error object here and next(err) appropriately, or if we possibly recovered from the error, simply next().
      res.status(err.status || 500);
      res.render(&#39;500&#39;, { error: err });
    });
    
    if (!module.parent) {// assigning to exports will not modify module, must use module.exports
      app.listen(3000);
      silent || console.log(&#39;Express started on port 3000&#39;);
    };



Error: No default engine was specified and no extension was provided

I am looking for a way to add a custom CA to NPM so I can download from a location using said certificate (an internal git-server) without having to nuke all CA-checking with

    npm config set strict-ssl false

Is there any way of achieving this or not? (if not: is there already a defect?)


npm add root CA

`npm install` / `npm install -g`  command is not working in Windows 7

Node.js is installed properly, node.js version is v0.10.28

&gt;Couldn&#39;t read dependencies  
&gt;ENOENT, open &#39;&quot;filepath&quot;\package.json&#39;  
&gt;This is most likely not a problem with npm itself.  
&gt;npm can&#39;t find a package.json file in your current directory.

    


   ![Photo](http://i.stack.imgur.com/wGoYc.jpg)

npm install gives error &quot;can&#39;t find a package.json file&quot;

I am new to node.js. I downloaded and install node.js installer from the [official site][1]. I have added this installer folder in PATH environment variable and I am able to run programs. But when I try to install some package using npm in node console it shows the error `npm should be run outside of the node repl, in your normal shell`. I also tried it on a separate console. But it shows command not found though I have added node in the environment variable. 

![enter image description here][2]

![enter image description here][3]


  [1]: http://nodejs.org/download/
  [2]: http://i.stack.imgur.com/gTQh7.png
  [3]: http://i.stack.imgur.com/4zySu.png

How to resolve &#39;npm should be run outside of the node repl, in your normal shell&#39;

I&#39;m developing two modules for NodeJS, first one named `aligator` and second one `aligator-methods`. Second one depends on first one to work. I&#39;m developing these two modules at the same time and I want to global link `aligator` so I can use it like it is on npm registry and I just installed it globally. To do this NPM documentation says that I need to use `npm link` but it&#39;s not working. 

File `package.json` of module `aligator`:

	{
	  &quot;name&quot;: &quot;aligator&quot;,
	  &quot;version&quot;: &quot;0.0.1&quot;,
	  &quot;description&quot;: &quot;&quot;,
	  &quot;main&quot;: &quot;index.js&quot;,
	  &quot;private&quot;: true,
	  &quot;directories&quot;: {
	    &quot;doc&quot;: &quot;docs&quot;,
	    &quot;example&quot;: &quot;examples&quot;,
	    &quot;test&quot;: &quot;spec&quot;
	  },
	  &quot;scripts&quot;: {
	    &quot;test&quot;: &quot;gulp jasmine&quot;
	  },
	  &quot;license&quot;: &quot;MIT&quot;,
	  &quot;devDependencies&quot;: {
	    &quot;gulp&quot;: &quot;^3.6.2&quot;,
	    &quot;gulp-jasmine&quot;: &quot;^0.2.0&quot;,
	    &quot;gulp-jshint&quot;: &quot;^1.6.1&quot;,
	    &quot;gulp-rename&quot;: &quot;^1.2.0&quot;,
	    &quot;jasmine-node&quot;: &quot;^1.14.3&quot;
	  },
	  &quot;dependencies&quot;: {
	    &quot;bluebird&quot;: &quot;^1.2.4&quot;,
	    &quot;lodash&quot;: &quot;^2.4.1&quot;,
	    &quot;mathjs&quot;: &quot;^0.22.0&quot;
	  }
	}

File `package.json` of module `aligator-methods`:

	{
	 &quot;name&quot;: &quot;aligator-methods&quot;,
	 &quot;version&quot;: &quot;0.0.1&quot;,
	 &quot;description&quot;: &quot;&quot;,
	 &quot;main&quot;: &quot;index.js&quot;,
	 &quot;private&quot;: true,
	 &quot;directories&quot;: {
	   &quot;doc&quot;: &quot;docs&quot;,
	   &quot;example&quot;: &quot;examples&quot;,
	   &quot;test&quot;: &quot;jasmine&quot;
	 },
	 &quot;scripts&quot;: {
	   &quot;test&quot;: &quot;gulp jasmine&quot;
	 },
	 &quot;author&quot;: &quot;&quot;,
	 &quot;license&quot;: &quot;MIT&quot;,
	 &quot;devDependencies&quot;: {
	   &quot;gulp&quot;: &quot;^3.6.2&quot;,
	   &quot;gulp-jasmine&quot;: &quot;^0.2.0&quot;,
	   &quot;gulp-jshint&quot;: &quot;^1.6.1&quot;,
	   &quot;gulp-rename&quot;: &quot;^1.2.0&quot;,
	   &quot;jasmine-node&quot;: &quot;^1.14.3&quot;
	 },
	 &quot;dependencies&quot;: {
	   &quot;lodash&quot;: &quot;^2.4.1&quot;,
	   &quot;mathjs&quot;: &quot;^0.22.0&quot;,
	   &quot;aligator&quot;: &quot;^0.0.1&quot;
	 }
	}


First of all I linked the module globally:

	$ cd ~/aligator
	$ npm link
	/usr/local/lib/node_modules/aligator -&gt; /Users/roc/aligator
	
This if I&#39;m not mistaken has created a global reference of my module `aligator` and now I can use this module from everywhere I want in the computer.

Then I went to the other module and tried to install the dependency but it gave me this output:

	$ cd ~/aligator-methods
	$ npm install
	npm ERR! 404 404 Not Found: aligator
	npm ERR! 404
	npm ERR! 404 &#39;aligator&#39; is not in the npm registry.
	npm ERR! 404 You should bug the author to publish it
	npm ERR! 404 It was specified as a dependency of &#39;aligator-methods&#39;
	npm ERR! 404
	npm ERR! 404 Note that you can also install from a
	npm ERR! 404 tarball, folder, or http url, or git url.
	
	npm ERR! System Darwin 13.2.0
	npm ERR! command &quot;node&quot; &quot;/usr/local/bin/npm&quot; &quot;install&quot;
	npm ERR! cwd /Users/roc/aligator-methods
	npm ERR! node -v v0.10.28
	npm ERR! npm -v 1.4.16
	npm ERR! code E404
	npm ERR!
	npm ERR! Additional logging details can be found in:
	npm ERR!     /Users/roc/aligator-methods/npm-debug.log
	npm ERR! not ok code 0

I even tried to link it directly with:
	
	$ cd ~/aligator-methods
	$ npm link aligator
	/Users/roc/aligator-methods/node_modules/aligator -&gt; /usr/local/lib/node_modules/aligator -&gt; /Users/roc/aligator
	
But it didn&#39;t work either.

**Any thoughts on what it is that could be happening?** I read somewhere that maybe it had something to do with my installation of **node** and **npm** because it was made by Homebrew and so sometimes I need to use `sudo`, it seemed unlikely but I tried what they proposed and It didn&#39;t work either.

NPM: After &quot;npm link&quot; module is not found

##Upon using a new terminal session in OS X, `nvm` forgets the node version and defaults to nothing:

`$ nvm ls`:

             .nvm
         v0.11.12
         v0.11.13

I have to keep hitting `nvm use v.0.11.13` in every session:

             .nvm
         v0.11.12
    -&gt;   v0.11.13

I&#39;ve tried both the `brew` install, as well as the official installation script.

My **`.profile`** for the brew version:

    #nvm
    export NVM_DIR=~/.nvm
    source $(brew --prefix nvm)/nvm.sh

And for the install.sh script:

`$ curl https://raw.githubusercontent.com/creationix/nvm/v0.10.0/install.sh | bash`

    #nvm
    export NVM_DIR=&quot;/Users/farhad/.nvm&quot;
    [ -s &quot;$NVM_DIR/nvm.sh&quot; ] &amp;&amp; . &quot;$NVM_DIR/nvm.sh&quot;  # This loads nvm

##Any clue to what I&#39;m doing wrong?

Content Type	Original Author	Original Content on Stackoverflow
Question	farwayer	View Question on Stackoverflow
Solution 1 - node.js	Gergo Erdosi	View Answer on Stackoverflow
Solution 2 - node.js	RoboMex	View Answer on Stackoverflow
Solution 3 - node.js	Atul	View Answer on Stackoverflow
Solution 4 - node.js	Alexander Mills	View Answer on Stackoverflow
Solution 5 - node.js	Vahid	View Answer on Stackoverflow

npm: disable postinstall script for package

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

Solution 2 - node.js

Solution 3 - node.js

Solution 4 - node.js

Solution 5 - node.js

Bootstrap throws Uncaught Error: Bootstrap's JavaScript requires jQuery

YAML Multi-Line Arrays

Attributions