node 5.x compatibility?

[kokujin]

At the moment, loads of complaints in the console during scaffolding

[jaumard]

Can you share your console output ?

[kokujin]

I am using Elementary OS Freya( Ubuntu 14.04) Node version 5.2.0

looks as if the warnings are all Hapi related. Here is a snippet

npm WARN installMany lodash was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany rc was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany trailpack-core was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany trailpack-hapi was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany trailpack-repl was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany trailpack-router was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany trails was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany waterline-sqlite3 was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN installMany winston was bundled with trails-test@0.0.0, but bundled package wasn't found in unpacked tree
npm WARN engine hoek@3.0.4: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine joi@7.1.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine hapi@11.1.4: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine vision@4.0.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine joi@7.1.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine joi@7.1.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine boom@3.1.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine items@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine isemail@2.1.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine topo@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine hoek@3.0.4: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine isemail@2.1.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine topo@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine hoek@3.0.4: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine isemail@2.1.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine topo@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine hoek@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine items@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine topo@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine boom@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine joi@7.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine cryptiles@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine mimos@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine heavy@4.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine kilt@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine subtext@3.0.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine iron@3.0.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine statehood@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine catbox-memory@2.0.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine ammo@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine peekaboo@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine call@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine accept@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine shot@2.0.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine catbox@7.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine wreck@7.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine pez@2.0.1: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine content@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine isemail@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine nigel@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine b64@3.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})
npm WARN engine vise@2.0.0: wanted: {"node":">=4.0.0"} (current: {"node":"0.12.9","npm":"2.14.9"})

[jaumard]

Warnings are because you're using node 0.12 not 5.2 current: {"node":"0.12.9","npm":"2.14.9"}

[kokujin]

I beg to differ, I am using, "n" (https://github.com/tj/n) to manage my node installations, this is my console version output:

╰─$ node -v
v5.2.0

n output:

   node/4.2.1
    node/5.0.0
  ο node/5.2.0

[tjwebb]

wanted: {"node":">=4.0.0"}

@kokujin you have some configuration issue, because your own machine thinks you're using some version older than 4.0.0. I would double-check this.

I am using, "n" (https://github.com/tj/n) to manage my node installations

fwiw, @troy0820 and I are also maintainers of n, so if you think something is broken there, let us know :)

[troy0820]

@kokujin Yeah, check the version in /usr/local/bin/node -v to see if it's outputting the correct version. Also check your PATH echo $PATH to see if that's in there. Also check which node you are using. You could be installing binaries from node and never be using them. If you ever installed node from apt-get .... it would've installed it to /usr/bin

[kokujin]

Thanks @tjwebb and @troy0820 for helping, I still have problems though. My console output

─$ which node && /usr/local/bin/node -v && echo $PATH                     1 ↵
/usr/local/bin/node
v5.2.0
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games

I will try clearing the npm cache und re-installing

[aclave1]

@kokujin what's the status on this? what version of npm are you running?

[tjwebb]

@kokujin if you're still having issues, let us know. Closing for now.