#1200 Node.js version problem amber init

npm WARN peerDependencies The peer dependency grunt-init@^0.3.1 included from amber-cli will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency bower@^1.3.9 included from amber-cli will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency latest-version@^1.0.1 included from amber-cli will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency grunt-cli@^0.1.13 included from amber-cli will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency 
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
/home/adrian/.npm-packages/bin/amber -> /home/adrian/.npm-packages/lib/node_modules/amber-cli/support/amber-cli.js
/home/adrian/.npm-packages/bin/amberc -> /home/adrian/.npm-packages/lib/node_modules/amber-cli/support/amberc-cli.js
amber-cli@0.14.15 /home/adrian/.npm-packages/lib/node_modules/amber-cli
├── grunt-init-amber@0.14.19
├── amber@0.14.16
└── amber-dev@0.7.1 (amdefine@1.0.0, requirejs-text@2.0.12, es6-promise@2.3.0, requirejs@2.1.20, amd-config-builder@0.2.2)

Welcome to Amber version 0.15.0-pre (NodeJS 4.0.0).
You are currently using Node.js v4.0.0
Required is at least Node.js v0.8.x or greater.

Originally at 2015-09-18T14:00:18Z by Adrian Castravete closed at 2015-09-19T18:05:55Z After running the `npm install -g amber-cli` I get the following output: ```log npm WARN peerDependencies The peer dependency grunt-init@^0.3.1 included from amber-cli will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. npm WARN peerDependencies The peer dependency bower@^1.3.9 included from amber-cli will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. npm WARN peerDependencies The peer dependency latest-version@^1.0.1 included from amber-cli will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. npm WARN peerDependencies The peer dependency grunt-cli@^0.1.13 included from amber-cli will no npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly. /home/adrian/.npm-packages/bin/amber -> /home/adrian/.npm-packages/lib/node_modules/amber-cli/support/amber-cli.js /home/adrian/.npm-packages/bin/amberc -> /home/adrian/.npm-packages/lib/node_modules/amber-cli/support/amberc-cli.js amber-cli@0.14.15 /home/adrian/.npm-packages/lib/node_modules/amber-cli ├── grunt-init-amber@0.14.19 ├── amber@0.14.16 └── amber-dev@0.7.1 (amdefine@1.0.0, requirejs-text@2.0.12, es6-promise@2.3.0, requirejs@2.1.20, amd-config-builder@0.2.2) ``` Which looks OK to me. I doubt the *warn*s have anything to do with the following... After trying to issue the `amber init` command in an empty directory I get the following output, tough: ```log Welcome to Amber version 0.15.0-pre (NodeJS 4.0.0). You are currently using Node.js v4.0.0 Required is at least Node.js v0.8.x or greater. ``` Any ideas whether I'm doing anything wrong?