Closed pavelbinar closed 10 years ago
Is that the exact command you ran? Those generators aren't part of phaser. Seems like it's something from yeoman.
well, it says in the log "node" "/usr/local/bin/npm" "i" "-g" "phaser" "--save-dev"
, but indeed it does look like yo phaser
or something. did you do yo
something and then && npm i -g phaser --save-dev
?
in any case we're thinking about renaming phaser b/c there is a JavaScript framework called phaser that I found after I published this, and they have a yeoman generator - but not a npm package.
Here is the full log from terminal: https://gist.github.com/pavelbinar/6b521452c0429dfdf30a
What about cache issue?
No yo
involved.
the part that causing an error is https://gist.github.com/pavelbinar/6b521452c0429dfdf30a#file-error-log-sh-L140-L142, which seems to be related to yeoman generators you have installed globally.
I get similar errors whenever I install something globally. it's because of how yeoman does peerDependencies - causes a lot of issues.
did you actually try running phaser? when I get similar errors it doesn't stop the package in question from actually installing
I think there's an issue with generator-karma
and/or generator-angular
. See this issue for more information.
As @jonschlinkert said, I think we need to update the docs because we made some changes and the actual phaser
library shouldn't be installed in global. Even though, I didn't know that peerDependencies in global modules would affect other other global modules.
Yes I tried to run phaser
command, but -bash: phaser: command not found
.
Here is full log: https://dl.dropboxusercontent.com/u/582525/assemble/npm-debug.log (1.7 MB)
sudo npm install phaser
is working
So no global install. All right so we may consider this as closed.
thanks for working with us on this! it's a new lib, we're still working out some bugs
I am getting this error at the end of npm installation log:
sudo npm i -g phaser --save-dev