yo angular generator error phantomjs install

[saqueib]

I have tried installing yo anugular and got below error, I have tried updating node, npm, npm cache clean etc. but its not working.

When I ran $ yo angular it goes and fetch dependencies using bower but its gives this error and move on

npm WARN engine karma@0.12.31: wanted: {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.0","npm":"2.5.0"})
...

> phantomjs@1.9.15 install 

/Users/jhondoe/Desktop/webapp/node_modules/karma-phantomjs-launcher/node_modules/phantomjs
> node install.js

Downloading https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-1.9.8-macosx.zip
Saving to /var/folders/vy/sc6v8frj4d3gprgzdpfcjhkm0000gn/T/phantomjs/phantomjs-1.9.8-macosx.zip
Receiving...
npm ERR! Darwin 13.0.0---------------------] 37% 0.0s|
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.0

npm ERR! null == true
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>
  [=======================================-] 98% 0.0s
Received 9187K total.
Extracting zip contents

and after that on more error and some warning

npm WARN unmet dependency /Users/jhondoe/Desktop/webapp/node_modules/grunt-contrib-jshint/node_modules/jshint/node_modules/cli/node_modules/glob requires minimatch@'0.3' but will load

and error

> pngquant-bin@2.0.3 postinstall 

/Users/jhondoe/Desktop/webapp/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-pngquant/node_modules/pngquant-bin
> node lib/install.js

  ✔ pngquant pre-build test passed successfully

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/jhondoe/Desktop/webapp/npm-debug.log
Loading "cssmin.js" tasks...ERROR
>> Error: Cannot find module 'pako/lib/zlib/messages'
Loading "uglify.js" tasks...ERROR
>> Error: Cannot find module 'pako/lib/zlib/messages'

after that it fails saying below msg

Loading "cssmin.js" tasks...ERROR
>> Error: Cannot find module 'pako/lib/zlib/messages'
Loading "uglify.js" tasks...ERROR
>> Error: Cannot find module 'pako/lib/zlib/messages'

...
Running "karma:unit" (karma) task
INFO [karma]: Karma v0.12.31 server started at http://localhost:8080/
INFO [launcher]: Starting browser PhantomJS
WARN [watcher]: Pattern "/Users/jhondoe/Desktop/webapp/test/mock/**/*.js" does not match any file.
INFO [PhantomJS 1.9.8 (Mac OS X)]: Connected on socket jYytgLM38t_yiNPOWqbq with id 15305149
PhantomJS 1.9.8 (Mac OS X): Executed 2 of 2 SUCCESS (0.004 secs / 0.02 secs)
Warning: Task "cssmin" not found. Use --force to continue.

Aborted due to warnings.

I am banging my head from long 6 hrs, please help how can i fix it.

my Node version is v0.12.0 NPM is 2.5.0 and OSX 10.9

[smikes]

For a long time, the only stable versions of node have been 0.8 and 0.10. This looks like at least part of your problem:

 {"node":"~0.8 || ~0.10"} (current: {"node":"0.12.0","

You may have the poor fortune to be one of the very first people to try this command with node@0.12.0. I would suggest that you try downgrading to 0.10.36 and see if things work then. If so, please open issues on the projects (eg karma) whose package.json is requiring explicit versions, not including the latest.

[saqueib]

Thanks @smikes it works after downgrading the node js to v0.10.30 with this warning

   npm WARN engine imagemin@3.1.0: wanted: {"node":">=0.10.0","npm":">=2.1.5"} (current: {"node":"0.10.30","npm":"1.4.21"})

[othiym23]

I have now seen three or four issues with Node 0.12 that all feature the spectacularly unhelpful failed assertion message

npm ERR! null == true

While npm isn't doing users any favors here, it can't, really, because every time you see this message, you're seeing an assertion that came from the guts of Node, without an accompanying stacktrace. When I've seen this in the past, it's been due to a problem with OpenSSL, but given the lack of available context (from the runtime -- there's not really anything npm can do here unless you run it at a very high loglevel, like -ddd), it's nearly impossible to say where it's coming from now. If someone can figure out what's causing these, it would be very useful to open up a bug on Node.

[othiym23]

See #7349 for further discussion of this, as I'm going to close this issue and use that one as the master issue for tracking this problem, which appears to be in Node.js's HTTPS handling code.