Cordova Ionic installation problems using UBUNTU

I have installed nodejs and npm
Moving on to the next installation (Then, install the latest Cordova and Ionic command-line tools) gives me errors. Please I need help urgently. Below are the errors:

> npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
> npm WARN engine cordova-serve@1.0.0: wanted: {“node”:">= 0.12.0",“npm”:">= 2.5.1"} (current: {“node”:“0.10.25”,“npm”:“1.4.21”})
> npm WARN engine deep-extend@0.4.1: wanted: {“node”:">=0.12.0",“iojs”:">=1.0.0"} (current: {“node”:“0.10.25”,“npm”:“1.4.21”})
> /usr/local/bin/cordova -> /usr/local/lib/node_modules/cordova/bin/cordova
> npm WARN package.json eyes@0.1.8 No repository field.
> npm WARN package.json faye-websocket@0.4.4 ‘repositories’ (plural) Not supported.
> npm WARN package.json Please pick one as the ‘repository’ field
> /usr/local/bin/ionic -> /usr/local/lib/node_modules/ionic/bin/ionic

> > node-sass@3.4.2 install /usr/local/lib/node_modules/ionic/node_modules/node-sass
> > node scripts/install.js

> sh: 1: node: not found
> npm WARN This failure might be due to the use of legacy binary “node”
> npm WARN For further explanations, please read
> /usr/share/doc/nodejs/README.Debian
**> **
> npm ERR! node-sass@3.4.2 install: node scripts/install.js
> npm ERR! Exit status 127
**> npm ERR! **
> npm ERR! Failed at the node-sass@3.4.2 install script.
> npm ERR! This is most likely a problem with the node-sass package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR! node scripts/install.js
> npm ERR! You can get their info via:
> npm ERR! npm owner ls node-sass
> npm ERR! There is likely additional logging output above.

> npm ERR! System Linux 4.2.0-30-generic
> npm ERR! command “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “cordova” “ionic”
> npm ERR! cwd /home/dr
> npm ERR! node -v v0.10.25
> npm ERR! npm -v 1.4.21
> npm ERR! code ELIFECYCLE
**> npm ERR! **
> npm ERR! Additional logging details can be found in:
> npm ERR! /home/dr/npm-debug.log
> npm ERR! not ok code 0