-
Notifications
You must be signed in to change notification settings - Fork 459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
typo on krakenjs.com #36
Comments
In my testing, the generator automatically pulled in yeoman, so I didn't need to specify it. Did it not work for you? |
I was able to duplicate this issue on OS X, while following instructions on krakenjs.com
|
Follow up: On my Ubuntu 13 machine I did not need the "yo" flag in npm to have it install. |
I'm also on OSX, so it looks like it's related to the node/npm version. I don't see anything specific mentioned in the npm changelog. @cdnsteve does this go away if you upgrade? Decision time: |
node -v Could be the culprit! Will update and get back |
I'd advise people upgrade to latest version: (using nvm is nice) It doesn't looks like you need the extra flag
|
Is still a valid issue? |
nope. |
…emove deps on winston
http://krakenjs.com/?utm_source=nodeweekly&utm_medium=email#Quick
written: sudo npm install -g generator-kraken
expected: sudo npm install -g yo generator-kraken
The text was updated successfully, but these errors were encountered: