npm error: [email protected] requires a peer of generator-mocha@>=0.1.6 but none was installed about generator-chromeapp HOT 5 CLOSED

Check version for yo and npm first and reinstall all of generators after npm clean cache

from generator-chromeapp.

Still the same :(

$ npm list -g --depth=0
/usr/local/lib
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

from generator-chromeapp.

Mmm...it do the same with generator-angular, and I see that this happens to more people, so I'll bother them ;) Thanks anyway! If I get a solution i'll share it here :)

from generator-chromeapp.

Ok, so is a npm3 related problem.
YO devs doesn't seems to like npm3 right now (they say it slow), and so they didn't change yo nether generator-angular with the 'new' specs:

We currently use peerDependencies to have external sub-generators installed automatically with the main generator, eg generator-mocha is a peerDependency in generator-webapp and installed with it.

npm3 will no longer install peerDependencies, which is a very good change, but will impact how we currently use it:

We will also be changing the behavior of peerDependencies in npm@3. We won’t be automatically downloading the peer dependency anymore. Instead, we’ll warn you if the peer dependency isn’t already installed. This requires you to resolve peerDependency conflicts yourself, manually, but in the long run this should make it less likely that you’ll end up in a tricky spot with your packages’ dependencies. - http://blog.npmjs.org/post/110924823920/npm-weekly-5

We should probably have sub-generators in dependencies instead.

So, I have to 'go back' to node 4.2.4 for the time being :(

from generator-chromeapp.

@arkdelkaos Thanks for your effort and close the issue now.

from generator-chromeapp.