You can run individual script entries using [`npm run SCRIPTNAME`](https://docs.npmjs.com/cli/run-script):

    $ npm run postinstall

When applying a transparent border over an element with a `linear-gradient` as the background, I get a weird effect.

![enter image description here][1]


  [1]: http://i.stack.imgur.com/bWlk6.png

Notice the left and right sides of the element don&#39;t have the proper colours (they&#39;re some way switched) and are weirdly *flat*.

**HTML**

    &lt;div class=&quot;colors&quot;&gt;
    &lt;/div&gt;


**CSS**

    .colors {
        width: 100px;
        border: 10px solid rgba(0,0,0,0.2);
        height: 50px;
        background: linear-gradient(to right, 
            #78C5D6,
            #459BA8,
            #79C267,
            #C5D647,
            #F5D63D,
            #F08B33,
            #E868A2,
            #BE61A5);
    }

*Why* is this showing a weird effect on the left and right side of the element, and *What* can I do about it?

Here is the fiddle: http://jsfiddle.net/fzndodgx/3/

Weird effect when applying transparent border over an element with a gradient background

Is it possible to copy Atom from one Mac to another, including all installed packages, settings etc?

How to share/transfer an Atom installation (packages and settings) from one Mac to another?

Just a simple question : in my node.js project, how could I just run the postinstall script, without running install before ?

FYI, this is my package.json :

    {
      &quot;name&quot;: &quot;gestionclientjs&quot;,
      ...,
      &quot;dependencies&quot;: {
		...
      },
      &quot;repository&quot;: {},
      &quot;devDependencies&quot;: {
		...
      },
      &quot;engines&quot;: {
        &quot;node&quot;: &quot;&gt;=0.10.0&quot;
      },
      &quot;scripts&quot;: {
        &quot;test&quot;: &quot;grunt test&quot;,
        &quot;postinstall&quot; : &quot;bower install &amp;&amp; node ./app/server/dbSeed.js&quot;,
        &quot;start&quot;: &quot;node app/server/app.js&quot;
      }
    }

For now, I run :

    npm install

in my project, but I want to run

    npm postinstall

when I want (and when I&#39;m sure dependencies are ok). 

NPM : how to just run post-install?

Just a simple question : in my node.js project, how could I just run the postinstall script, without running install before ?
FYI, this is my package.json :
<pre><code class="hljs language-json">{
 "name": "gestionclientjs",
 ...,
 "dependencies": {
	...
 },
 "repository": {},
 "devDependencies": {
	...
 },
 "engines": {
 "node": ">=0.10.0"
 },
 "scripts": {
 "test": "grunt test",
 "postinstall" : "bower install &#x26;&#x26; node ./app/server/dbSeed.js",
 "start": "node app/server/app.js"
 }
}
</code></pre>
For now, I run :
<pre><code class="hljs">npm install
</code></pre>
in my project, but I want to run
<pre><code class="hljs">npm postinstall
</code></pre>
when I want (and when I'm sure dependencies are ok).

What is a good aproach to handle background processes in a NodeJS application? 

**Scenario**: After a user posts something to an app I want to crunch the data, request additional data from external resources, etc. All of this is quite time consuming, so I want it out of the req/res loop. Ideal would be to just have a queue of jobs where you can quickly dump a job on and a daemon or task runner will always take the oldest one and process it.

In RoR I would have done it with something like Delayed Job. What is the Node equivalent of this API?



Background processes in Node.js

    /*Making http request to the api (Git hub)
    create request
    parse responce
    wrap in a function
    */
    var https = require(&quot;https&quot;);

    var username = &#39;lynndor&#39;;
    //CREATING AN OBJECT
    var options = {
	    host: &#39;api.github.com&#39;,
	    path: &#39; /users/&#39;+ username +&#39;/repos&#39;,
	    method: &#39;GET&#39;
    };

    var request = https.request(options, function(responce){
	    var body = &#39;&#39;
	    responce.on(&quot;data&quot;, function(chunk){
		    body += chunk.toString(&#39;utf8&#39;)
	    });
	    responce.on(&quot;end&quot;, function(){
		    console.log(&quot;Body&quot;, body);
	    });
    });
    request.end();

&gt; Im trying to create a request to the git hub api, the aim is to get the list repository for the specified you, but i keep getting the above mentioned error, please help

TypeError: Request path contains unescaped characters, how can I fix this

i tried to install grunt on a mac with Yosemite. node is already installed in the newest version. if i type &quot;node -v&quot; in the terminal i get the line v0.12.5. thats good. but when i want to install something with npm i get only a error... 

i tried &quot;sudo npm install -g grunt-cli&quot;, &quot;sudo npm install npm -g&quot; and also with  &quot;npm -v&quot; i get always this error... 

    Error: Cannot find module &#39;are-we-there-yet&#39;
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.&lt;anonymous&gt; (/usr/local/Cellar/node/0.10.22/lib/node_modules/npm/node_modules/npmlog/log.js:2:16)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)

someone knows what&#39;s the problem or better a solution?


npm doesn&#39;t work, get always this error -&gt; Error: Cannot find module &#39;are-we-there-yet&#39;

Can someone explain how to fix a missing config error with Node.js? I&#39;ve followed all the examples from the [aws doc page](http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/node-configuring.html) but I still get this error no matter what.

    { [ConfigError: Missing region in config]
    message: &#39;Missing region in config&#39;,
    code: &#39;ConfigError&#39;,
    time: Wed Jun 24 2015 21:39:58 GMT-0400 (EDT) }&gt;{ thumbnail: 
     { fieldname: &#39;thumbnail&#39;,
     originalname: &#39;testDoc.pdf&#39;,
     name: &#39;testDoc.pdf&#39;,
     encoding: &#39;7bit&#39;,
     mimetype: &#39;application/pdf&#39;,
    path: &#39;uploads/testDoc.pdf&#39;,
     extension: &#39;pdf&#39;,
     size: 24,
     truncated: false,
     buffer: null } }
     POST / 200 81.530 ms - -

Here is my code:

    var express = require(&#39;express&#39;);
    var router = express.Router();
    var AWS = require(&#39;aws-sdk&#39;);
    var dd = new AWS.DynamoDB();
    var s3 = new AWS.S3();
    var bucketName = &#39;my-bucket&#39;;
    
    AWS.config.update({region:&#39;us-east-1&#39;});

    (...)

Configuring region in Node.js AWS SDK

When I try to use webpack with a simple express server I always get TONS of errors: 
**express.js**

    &#39;use strict&#39;;
    var express = require(&#39;express&#39;);
    var path = require(&#39;path&#39;);
    var url = require(&#39;url&#39;);


    // -------- my proxy----------------------
    var app = express();
    app.set(&#39;views&#39;, path.join(__dirname, &#39;views&#39;));
    app.set(&#39;view engine&#39;, &#39;ejs&#39;);
    app.set(&#39;port&#39;, process.env.PORT || 8080);
    app.use(function logErrors(err, req, res, next) {
            console.error(err.stack);
            next(err);
        }
    );

    app.listen(app.get(&#39;port&#39;), function() {
        console.info(&#39;Express server started at http://localhost:&#39; + app.get(&#39;port&#39;));
    });



I get all those errors:

    Version: webpack 1.10.0
    Time: 1200ms
      Asset    Size  Chunks             Chunk Names
    outfile  559 kB       0  [emitted]  main
    chunk    {0} outfile (main) 498 kB [rendered]
        [0] ../app/server/express2.js 553 bytes {0} [built]
         + 125 hidden modules

    WARNING in ../~/express/lib/view.js
    Critical dependencies:
    78:29-56 the request of a dependency is an expression
     @ ../~/express/lib/view.js 78:29-56

    ERROR in ../~/express/lib/request.js
    Module not found: Error: Cannot resolve module &#39;net&#39; in /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/lib
     @ ../~/express/lib/request.js 18:11-25

    ERROR in ../~/express/lib/view.js
    Module not found: Error: Cannot resolve module &#39;fs&#39; in /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/lib
     @ ../~/express/lib/view.js 18:9-22

    ERROR in ../~/express/~/send/index.js
    Module not found: Error: Cannot resolve module &#39;fs&#39; in /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/send
     @ ../~/express/~/send/index.js 25:9-22

    ERROR in ../~/express/~/etag/index.js
    Module not found: Error: Cannot resolve module &#39;fs&#39; in /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/etag
     @ ../~/express/~/etag/index.js 22:12-25

    ERROR in ../~/express/~/send/~/destroy/index.js
    Module not found: Error: Cannot resolve module &#39;fs&#39; in /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/send/node_modules/destroy
     @ ../~/express/~/send/~/destroy/index.js 1:17-30

    ERROR in ../~/express/~/send/~/mime/mime.js
    Module not found: Error: Cannot resolve module &#39;fs&#39; in /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/send/node_modules/mime
     @ ../~/express/~/send/~/mime/mime.js 2:9-22

    ERROR in ../~/express/~/send/~/statuses/codes.json
    Module parse failed: /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/send/node_modules/statuses/codes.json Line 2: Unexpected token :
    You may need an appropriate loader to handle this file type.
    | {
    |   &quot;100&quot;: &quot;Continue&quot;,
    |   &quot;101&quot;: &quot;Switching Protocols&quot;,
    |   &quot;102&quot;: &quot;Processing&quot;,
     @ ../~/express/~/send/~/statuses/index.js 2:12-35

    ERROR in ../~/express/~/send/~/mime/types.json
    Module parse failed: /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/send/node_modules/mime/types.json Line 1: Unexpected token :
    You may need an appropriate loader to handle this file type.

    |
     @ ../~/express/~/send/~/mime/mime.js 87:12-35

    ERROR in ../~/express/~/accepts/~/mime-types/~/mime-db/db.json
    Module parse failed: /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/accepts/node_modules/mime-types/node_modules/mime-db/db.json Line 2: Unexpected token :
    You may need an appropriate loader to handle this file type.
    | {
    |   &quot;application/1d-interleaved-parityfec&quot;: {
    |     &quot;source&quot;: &quot;iana&quot;
    |   },
     @ ../~/express/~/accepts/~/mime-types/~/mime-db/index.js 11:17-37

    ERROR in ../~/express/~/type-is/~/mime-types/~/mime-db/db.json
    Module parse failed: /Users/Dynopia/Development/DS_Stalker_Frontend/node_modules/express/node_modules/type-is/node_modules/mime-types/node_modules/mime-db/db.json Line 2: Unexpected token :
    You may need an appropriate loader to handle this file type.
    | {
    |   &quot;application/1d-interleaved-parityfec&quot;: {
    |     &quot;source&quot;: &quot;iana&quot;
    |   },
     @ ../~/express/~/type-is/~/mime-types/~/mime-db/index.js 11:17-37

and this is my config file:

    var webpack = require(&#39;webpack&#39;);
    
    
    module.exports = {
        // Makes sure errors in console map to the correct file
        // and line number
        devtool: &#39;eval&#39;,
        entry: [
            &#39;./bin/www.js&#39;
        ],
        output: {
            path: &#39;./bin/out&#39;,
            filename: &#39;server.js&#39;
        },
    
        extensions: [
            &#39;&#39;,
            &#39;.jsx&#39;, &#39;.js&#39;
        ],
    
        module: {
    
            loaders: [
                // Compile es6 to js.
                {
                    test: /app\/.*\.js?$/,
                    loaders: [
                        &#39;react-hot&#39;,
                        &#39;babel-loader&#39;
                    ]
                }
            ]
        },
    
        devtool: &#39;source-map&#39;
    };


What can I do, I need to use webpack on my server side as well.

I run the express.js file like so:
`./node_modules/webpack/bin/webpack.js ../app/server/express.js outfile --display-chunks -c --progress -d`

How can I use webpack with express?

Given the following directory structure:

    my-project
    |
    |-- node_modules
        |
        |-- react
        |-- module-x
            |
            |--node_modules
                |
                |--react

You can see both **my-project** and **module-x** require React.  I have the same problem as described on [this question](https://stackoverflow.com/questions/28519287/what-does-only-a-reactowner-can-have-refs-mean), but the suggestion is to remove react from the package.json dependencies.  I do that and it works fine, as long as no node_modules are installed in **module-x**, because Webpack will use React from **my-project**.  But if I&#39;m in the process of developing **module-x** and the node_modules are installed, Webpack uses React from both **my-project** and **module-x**.

Is there a way I could have Webpack make sure only one instance of React is used, even though it&#39;s required on two separate levels?

I know I could keep **module-x** in a separate directory when developing, but it seems like I&#39;d have to publish it and then install it in **my-project** to test it, and that&#39;s not very efficient.  I thought about `npm link`, but had no luck with it since it still has node_modules installed in **module-x**.

[This here](https://github.com/webpack/webpack/issues/105) sounds a lot like the same challenge I&#39;m having, but it doesn&#39;t seem like `npm dedupe` or Webpack&#39;s dedupe option would work.  I&#39;m probably not understanding some important detail.

How to avoid React loading twice with Webpack when developing

I am trying to update npm itself:

    npm uninstall npm -g

Responds with:

    unbuild npm@2.12.1

But when I go:

    npm --version

I get 1.4.28? How to upgrade the npm itself?

How can I update npm itself?

I&#39;m extremely new to Node and trying to get my head around app basics. I&#39;m curious as to why these two commands:

&gt; node app.js

--vs--

&gt; npm start

output the same thing to the console and appear to continue &quot;listening&quot;, but why when I try to access http://localhost:3000 I get a 404 only when running the first command.

I see that Express 4 seems to have a different app structure, but why is it that one successfully listens and the other doesn&#39;t, despite the same behavior in the console?

Any explanation is helpful. Thanks!

npm start vs node app.js

I&#39;m trying to upgrade to the latest version of node. I&#39;m following the instructions at http://davidwalsh.name/upgrade-nodejs

But when I do:

    sudo npm install -g n

I get the error:

    sudo: npm: command not found

npm works without sudo. When I do:

    whereis node

I see:

    node: /usr/bin/node /usr/lib/node /usr/bin/X11/node /usr/local/node

Running:

    which npm

Shows:

    /usr/local/node/bin/npm

I tried the solution at https://stackoverflow.com/a/5062718/1246159

But I&#39;m still getting the same error. I also looked at the /etc/sudoers file and the relevant line is:

    Defaults        secure_path=&quot;/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin&quot;


This looks fine to me. How can I possibly get NPM working with sudo command?


sudo: npm: command not found

I&#39;m receiving this error when trying to debug my node application using the `npm start` command.

#### Error:

&lt;!-- language: lang-none --&gt;

    npm ERR! Windows_NT 6.3.9600
    npm ERR! argv &quot;C:\\Program Files\\nodejs\\\\node.exe&quot; &quot;C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js&quot; &quot;start&quot;
    npm ERR! node v0.12.7
    npm ERR! npm  v2.11.3
    
    npm ERR! missing script: start
    npm ERR!
    npm ERR! If you need help, you may report this error at:
    npm ERR!     &lt;https://github.com/npm/npm/issues&gt;npm ERR! Please include the following file with any support request:
    npm ERR!     C:\Users\andrmoll.NORTHAMERICA\Documents\GitHub\SVIChallenge\npm-debug.log
 

#### From the debug file:

&lt;!-- language: lang-none --&gt;

    Error: missing script: start
           at run (C:\Program Files\nodejs\node_modules\npm\lib\run-script.js:142:19)
           at C:\Program Files\nodejs\node_modules\npm\lib\run-script.js:58:5
           at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:345:5
           at checkBinReferences_ (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:309:45)
           at final (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:343:3)
           at then (C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:113:5)
           at C:\Program Files\nodejs\node_modules\npm\node_modules\read-package-json\read-json.js:300:12
           at evalmachine.&lt;anonymous&gt;:334:14
           at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:102:5
           at FSReqWrap.oncomplete (evalmachine.&lt;anonymous&gt;:95:15)


Start script missing error when running npm start

NPM 2.11.3

I&#39;m building a library in Node. This library is only for use by the company I am currently working for. I think this means that the license is &quot;None&quot;. But when I `npm init` it wants me to use an SPDX License. &quot;None&quot; or &quot;Unlicensed&quot; are not valid options. 

`npm WARN package.json data_monitoring_api@0.1.0 license should be a valid SPDX license expression`

There is some discussion around this on the NPM GitHub issue tracker but I can&#39;t find anything that definitively answers this. Perhaps NPM doesn&#39;t support this concept, but that seems odd. 

What should I put for this field in this case? I&#39;d like to get rid of the npm warnings related to this. 

While the docs say that UNLICENSED is valid, it still gives a warning: 

    $ cat package.json | grep licen
      &quot;license&quot;: &quot;UNLICENSED&quot;,
    
    $ npm install 
    npm WARN package.json data_monitoring_api@0.1.0 license should be a valid SPDX license expression

What should I put in the license field of package.json if my code is only for use by the company I work for?

In js file, i used import to instead of require

    import co from &#39;co&#39;;

And tried to run it directly by nodejs since it said import is &#39;shipping features&#39; and support without any runtime flag (https://nodejs.org/en/docs/es6/), but i got an error

    import co from &#39;co&#39;;
    ^^^^^^

    SyntaxError: Unexpected token import

Then i tried to use babel

    npm install -g babel-core
    npm install -g babel-cli
    npm install babel-core //install to babel locally, is it necessary?

and run by 

    babel-node js.js

still got same error, unexpected token import?

How could I get rid of it?


&quot;unexpected token import&quot; in Nodejs5 and babel?

Because we don&#39;t want sensitive data in the project code, including the package.json file, using environment variables would be a logical choice in my opinion.

Example package.json:

      &quot;dependencies&quot;: {
        &quot;accounting&quot;: &quot;~0.4.0&quot;,
        &quot;async&quot;: &quot;~1.4.2&quot;,
        &quot;my-private-module&quot;:&quot;git+https://${BB_USER}:${BB_PASS}@bitbucket.org/foo/bar.git&quot;

Is this possible?

The question is *not* if this is *wise* or *not good*, just **if it&#39;s possible**.

How to use environment variables in package.json

How do I display the app version in angular application? the version should be taken from `package.json` file

    {
      &quot;name&quot;: &quot;angular-app&quot;,
      &quot;version&quot;: &quot;0.0.1&quot;,
      ...
    }

In angular 1.x, I have this html:

    &lt;p&gt;&lt;%=version %&gt;&lt;/p&gt;

In angular, this is not rendered as version number, but instead just printed as it is (`&lt;%=version %&gt;` instead of `0.0.1`).



Content Type	Original Author	Original Content on Stackoverflow
Question	noelm	View Question on Stackoverflow
Solution 1 - node.js	robertklep	View Answer on Stackoverflow

NPM : how to just run post-install?

node.js Problem Overview

node.js Solutions

Solution 1 - node.js

How to share/transfer an Atom installation (packages and settings) from one Mac to another?

Weird effect when applying transparent border over an element with a gradient background

Attributions