removing manually:

    cd ~/.nvm/versions/node
    sudo rm -rf v4.2.3/

Remove by command 

    nvm uninstall &lt;version&gt; 
    nvm uninstall v16.7.0

remove manually

    cd ~/.nvm/versions/node
    sudo rm -rf v16.7.0/



    cd ~/.nvm/versions/node
    rm -Rf v4.2.3

Try clearing cash
nvm cache clear

It works now, in nvm version 0.35.1. Or at least it worked for me.

If the node version we want to uninstall is the currently used one though, before uninstalling it we need to `nvm use` another version.

nvm deactivate
then 
nvm uninstall 4.2.3 or (version number)

it will work.

I&#39;ve got Angular [reactive form][1]. I created `formControl`s and assigned it to input fields by`[formControl]=...`. As I understand it creates `nativeElement &lt;-&gt; formControl` link.

My question: is it possible to get `nativeElement` for `formControl`? I want to do something like `myFormControl.nativeElement.focus()`


  [1]: https://angular.io/docs/ts/latest/cookbook/dynamic-form.html

Is it possible to get native element for formControl?

How to change the switch component&#39;s size in React Native?

    &lt;Switch onValueChange={this._changeReciveNotice.bind(this)}
            value={this.state.isReciveNotice}
            style={{width:20,height:10}}/&gt;


this style code doesn&#39;t effect 

How to change the switch component&#39;s size in React Native?

So I&#39;m trying to clear out older versions of node.js.

I start with:

    $ nvm ls
          v0.10.30
          v4.2.3
    -&gt;    v6.6.0
          system

I don&#39;t want the older versions, so I then do:

    $ nvm uninstall 4.2.3
    Uninstalled node v4.2.3

I then verify that it&#39;s done what I wanted, but it gives the *same* list of installed versions as before:

    $ nvm ls
          v0.10.30
          v4.2.3
    -&gt;    v6.6.0
          system

Specifically, `v4.2.3` is still there.

Any ideas what I might be doing wrong?  Any other way to force the uninstall?  I&#39;m using the Cloud 9 IDE.



nvm uninstall doesn&#39;t actually uninstall the node version

So I'm trying to clear out older versions of node.js.
I start with:
<pre><code class="hljs language-shell">$ nvm ls
 v0.10.30
 v4.2.3
-> v6.6.0
 system
</code></pre>
I don't want the older versions, so I then do:
<pre><code class="hljs language-ruby">$ nvm uninstall 4.2.3
Uninstalled node v4.2.3
</code></pre>
I then verify that it's done what I wanted, but it gives the same list of installed versions as before:
<pre><code class="hljs language-shell">$ nvm ls
 v0.10.30
 v4.2.3
-> v6.6.0
 system
</code></pre>
Specifically, <code>v4.2.3</code> is still there.
Any ideas what I might be doing wrong? Any other way to force the uninstall? I'm using the Cloud 9 IDE.

I was attempting to chain two async functions together, because the first had a conditional return parameter that caused the second to either run, or exit the module. However, I&#39;ve found odd behavior I can&#39;t find in the specs.

    async function isInLobby() {
        //promise.all([chained methods here])
        let exit = false;
        if (someCondition) exit = true;
    }

This is a bastardized snippet of my code (you can see the full scope [here](https://github.com/RUJodan/SourceUndead/blob/master/routes/lobby.js#L53)), that simply checks if a player if already in a lobby, but that&#39;s irrelevant.

Next we have this async function.

    async function countPlayer() {
        const keyLength = await scardAsync(game);
        return keyLength;
    }

This function doesn&#39;t need to run if `exit === true`.

I tried to do

    const inLobby = await isInLobby();

This I hoped would await to results, so I can use `inLobby` to conditionally run `countPlayer`, however I received a typeerror with no specific details.

Why can&#39;t you `await` an `async` function outside of the scope of the function? I know it&#39;s a sugar promise, so it must be chained to `then` but why is it that in `countPlayer` I can await another promise, but outside, I can&#39;t `await` `isInLobby`?

Using await outside of an async function

So, I&#39;m testing a component that relies on an event-emitter. To do so I came up with a solution using Promises with Mocha+Chai:

    it(&#39;should transition with the correct event&#39;, (done) =&gt; {
      const cFSM = new CharacterFSM({}, emitter, transitions);
      let timeout = null;
      let resolved = false;
      new Promise((resolve, reject) =&gt; {
        emitter.once(&#39;action&#39;, resolve);
        emitter.emit(&#39;done&#39;, {});
        timeout = setTimeout(() =&gt; {
          if (!resolved) {
            reject(&#39;Timedout!&#39;);
          }
          clearTimeout(timeout);
        }, 100);
      }).then((state) =&gt; {
        resolved = true;
        assert(state.action === &#39;DONE&#39;, &#39;should change state&#39;);
        done();
      }).catch((error) =&gt; {
        assert.isNotOk(error,&#39;Promise error&#39;);
        done();
      });
    });

On the console I&#39;m getting an &#39;UnhandledPromiseRejectionWarning&#39; even though the reject function is getting called since it instantly shows the message &#39;AssertionError: Promise error&#39;

&gt; (node:25754) UnhandledPromiseRejectionWarning: Unhandled promise
&gt; rejection (rejection id:  2): AssertionError: Promise error: expected
&gt; { Object (message, showDiff, ...) } to be falsy
&gt; 1) should transition with the correct event

And then, after 2 sec I get 

&gt;  Error: timeout of 2000ms exceeded. Ensure the done() callback is
&gt; being called in this test.

Which is even weirder since the catch callback was executed(I think that for some reason the assert failure prevented the rest of the execution)  
   
Now the funny thing, if I comment out the `assert.isNotOk(error...)` the test runs fine without any warning in the console. It stills &#39;fails&#39; in the sense that it executes the catch.  
But still, I can&#39;t understand these errors with promise. Can someone enlighten me?

Getting a UnhandledPromiseRejectionWarning when testing using mocha/chai

Can anyone explain me what is `node-gyp` and why it uses my system files to build Node.JS packages.

 1. If Ii build a node project and it used `node-gyp` internally.
 2. Then I just tar that project and moved to a different system
 3. I untar it there and try to use it 

Will this approach work?

What is node-gyp

npm update does not do anything

I have an app using passport.js to log in users through facebook, and am attempting to use express-mysql-session to persist their login states. If I don&#39;t include the express-mysql-session code, the passport serializeUser and deserializeUser functions hit fine...however when I un-comment the code that attempts to store their session with express-mysql-session, the deserializeUser function doesn&#39;t get hit, and the user never gets properly logged in.

server.js file

    var express      = require(&#39;express&#39;);
    var mysql		 = require(&#39;mysql&#39;);
    var passport     = require(&#39;passport&#39;);
    var session      = require(&#39;express-session&#39;);
    var MySQLStore   = require(&#39;express-mysql-session&#39;)(session);
    
    if (typeof process.env.OPENSHIFT_MYSQL_DB_HOST === &quot;undefined&quot;){
    	var options = {
    		host     : &#39;localhost&#39;,
    		port     : &#39;3307&#39;,
    		user     : &#39;user&#39;,
    		password : &#39;password&#39;,
    		database : &#39;database&#39;,
    		socketpath: &#39;/var/run/mysqld/mysqld.sock&#39;
    	}
    } else { 
    	var options = {
    		host     : process.env.OPENSHIFT_MYSQL_DB_HOST,
    		port     : process.env.OPENSHIFT_MYSQL_DB_PORT,
    		user     : process.env.OPENSHIFT_MYSQL_DB_USERNAME,
    		password : process.env.OPENSHIFT_MYSQL_DB_PASSWORD,
    		database : process.env.OPENSHIFT_APP_NAME,
    		socket	 : process.env.OPENSHIFT_MYSQL_DB_SOCKET
    	}
    };	  
    
    var connection = mysql.createConnection(options);
    
    var sessionStore = new MySQLStore({
        checkExpirationInterval: 900000,// How frequently expired sessions will be cleared; milliseconds.
        expiration: 86400000,// The maximum age of a valid session; milliseconds.
        createDatabaseTable: false,// Whether or not to create the sessions database table, if one does not already exist.
    	connectionLimit: 1,
        schema: {
            tableName: &#39;LoginRequests&#39;,
            columnNames: {
                session_id: &#39;loginID&#39;,
                expires: &#39;expires&#39;,
    			data:&#39;data&#39;
            }
        }
    }, connection);

     self.initializeServer = function() {
            self.app = module.exports = express();
            self.app.configure(function() {
    			self.app.set(&#39;views&#39;, __dirname + &#39;/public&#39;);
                self.app.set(&#39;view engine&#39;, &#39;html&#39;);
    			self.app.engine(&#39;html&#39;, require(&#39;hogan-express&#39;));
    			self.app.enable(&#39;view cache&#39;);
                self.app.use(express.favicon());
                self.app.use(express.logger(&#39;dev&#39;));
                self.app.use(express.bodyParser());
                self.app.use(express.methodOverride());
                self.app.use(express.cookieParser(&#39;secret&#39;));
    			self.app.use(session({
    			    key: &#39;session_cookie_name&#39;,
    			    secret: &#39;secret&#39;,
    			    cookie: {maxAge: 3600000, secure:false},
    			    store: sessionStore,
    			    resave: false,
    			    saveUninitialized: false
    			}));
    			// required for passport
    			self.app.use(passport.initialize());
    			self.app.use(passport.session()); // persistent login sessions
                self.app.use(express.static(path.join(__dirname, &#39;public&#39;)));
                self.app.use(&#39;/public&#39;,express.static(__dirname, &#39;/public&#39;));
                self.app.use(self.app.router);
                //self.app.use(require(&#39;stylus&#39;).middleware(__dirname + &#39;/public&#39;));
    
    			
    		});
            
        require(&#39;./routes/site.js&#39;);  
    	require(&#39;./config/passport.js&#39;)(passport); // pass passport for configuration 
    	 
        }

So, if I comment out the &quot;store&quot; option in the session object above, the passport functions get hit. If I leave this line un-commented, the deserializeUser function does not get hit. 

Passport functions

    passport.serializeUser(function(user, done) {
    		console.log(&#39;you have been serialized!&#39;);
    			done(null, user.id);
    	});
     	
    	
    	// used to deserialize the user
    	passport.deserializeUser(function(id, done) {
    		console.log(&#39;you have been deserialized!&#39;);
    		connection.query(&quot;SELECT * FROM Users WHERE id = &quot;+id,function(err,rows){
    			done(err, rows[0]);
    		});
    	});

EDIT

Mor Paz suggested that I include some of the logs from when I run my server with the debug module. Below are the logs right before, and immediately after the user is serialized. The user should be deserialized at some point near this, but never is.

    GET /auth/facebook 302 81ms - 412b
    express-mysql-session:log Getting session: oNcJ4UapxCY_zKOyfSBTUWaVhaNZuFRq +356ms
    you are a user!
    you have been serialized!
      express-mysql-session:log Setting session: tgRPY-Mb1VDP2zaSMOFhlf_IWFhVpTia +798ms
      express-mysql-session:log Getting session: tgRPY-Mb1VDP2zaSMOFhlf_IWFhVpTia +6ms
    GET /auth/facebook/callback?    code=AQCWPvA5ZRMYoTueW6_wWU49Up5ggjW68ufOtiYkU5IzhRjSNyyWnzlQVprgQo_uubQkEVvNI0yo53ET3cWBnDAHUGmAXPBy_ITEmC-biE2KEGEr0iCm_cqjuG90nnePY-k9U2oFUbX2kvLgMeM0kZ-094EHiU_NJjmAJNj6mzTkSE47935RhJy0Tba_sYS88_C0N3kn5f5kcoTC4KsgW1gBHWWJAwZ68Lj94ffVe2hN97580CtzEpJa0wwQHwTBYfmjQ0NfUdx07m4rXW9R7PR06aHDcUDrYqR9Kb0LWq4sZLbQjV5rI7gzkWG-huhq7IY 302 825ms - 72b
      express-mysql-session:log Setting session: Xo9OjfmJzTFp1CSF6srLi_UyxTCLg-EI +56ms
      express-mysql-session:log Getting session: Xo9OjfmJzTFp1CSF6srLi_UyxTCLg-EI +23ms
      express-mysql-session:log Getting session: Xo9OjfmJzTFp1CSF6srLi_UyxTCLg-EI +2ms
    GET /profile 200 84ms - 4.22kb


Express-mysql-session preventing passport deserializeUser from running

Is it possible for VS Code to use node version specified by NVM? 

I have 6.9.2 installed locally. Even after switching to another version, from the OS X terminal (not the VS Code terminal), restarting VS Code, VS Code still shows using 6.9.2.

**OS X terminal**

    MacBook-Pro-3:~ mac$ node -v
    v7.8.0

**VS Code Terminal**

    MacBook-Pro-3:QB-Invoice-API mac$ node -v
    v6.9.2

Visual Studio Code to use node version specified by NVM

For example I want to install either 7.9 or 7.10 but want to avoid Node 8 due to the `webpack node-sass` breaking bug.

When I run `brew search node` this is what I see:

&gt; ❯ brew search node
leafnode        llnode          node ✔          node-build      &gt; node@0.10       node@0.12       node@4          node@6          nodebrew        nodeenv         nodenv
caskroom/cask/node-profiler

&gt; If you meant &quot;node&quot; specifically:
It was migrated from caskroom/cask to homebrew/core.
You can access it again by running:
  brew tap homebrew/core

There is node which is checked (my current version is `v7.4.0` then `node@0.10`, `node@0.12`, `node@4` and `node@6`?

The reason I can&#39;t just fully upgrade to 8 is node-sass won&#39;t work in webpack.


----------


## Just installed NVM and got this crazy error log:

`=&gt; nvm source string already in /Users/leongaban/.zshrc
=&gt; Appending bash_completion source string to /Users/leongaban/.zshrc
npm ERR! missing: is-path-cwd@^1.0.0, required by del@3.0.0
npm ERR! missing: is-path-in-cwd@^1.0.0, required by del@3.0.0
npm ERR! missing: p-map@^1.1.1, required by del@3.0.0
npm ERR! missing: pify@^3.0.0, required by del@3.0.0
npm ERR! missing: rimraf@^2.2.8, required by del@3.0.0
npm ERR! missing: bluebird@^3.1.1, required by gulp-html-replace@1.6.2
npm ERR! missing: clone@^1.0.2, required by gulp-html-replace@1.6.2`

...

    =&gt; You currently have modules installed globally with `npm`. These will no
    =&gt; longer be linked to the active version of Node when you install a new node
    =&gt; with `nvm`; and they may (depending on how you construct your `$PATH`)
    =&gt; override the binaries of modules installed with `nvm`:


If I&#39;m reading this right, does this mean I can&#39;t use `npm` to globally install packages anymore and have to use `nvm`?

### Update

I added the export lines to my **.zshrc** bash (I don&#39;t use bash_profile)

    ❯ nvm --version
    0.33.2

How to brew install specific version of Node?

In the system there is a `nodejs`, installed through `nvm`. The command is not running `npm`.
Console is `Oh my zsh`

How to run &quot;nvm&quot; in &quot;oh my zsh&quot;?

I have installed nvm (ubuntu with zsh shell) with two node version: `v6.11.5` and `v9.0.0` and the default version in nvm is the `v9.0.0` 

Every time I need to change the node version 

    $ nvm list
             v6.11.5
    -&gt;       v9.0.0
             system
    default -&gt; node (-&gt; v9.0.0)
    node -&gt; stable (-&gt; v9.0.0) (default)
    stable -&gt; 9.0 (-&gt; v9.0.0) (default)
   

    $ nvm v6

How could I change the nvm version default to define `v6.11.5`? 





How can the default node version be set using NVM?

I have `nvm` setup to use the latest long term support version in `~/.nvm/alias/default`, by setting it to `lts/*`.

When I try and have my shell initialize my nvm version (zsh), I get the following error:

&gt; N/A: version &quot;N/A -&gt; N/A&quot; is not yet installed.

Why is this happening?

Content Type	Original Author	Original Content on Stackoverflow
Question	drmrbrewer	View Question on Stackoverflow
Solution 1 - node.js	sudo	View Answer on Stackoverflow
Solution 2 - node.js	MADHUR GUPTA	View Answer on Stackoverflow
Solution 3 - node.js	Flavio Lima	View Answer on Stackoverflow
Solution 4 - node.js	silvanasono	View Answer on Stackoverflow
Solution 5 - node.js	Tino Jose Thannippara	View Answer on Stackoverflow

nvm uninstall doesn't actually uninstall the node version

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

How to change the switch component's size in React Native?

Is it possible to get native element for formControl?

Attributions