search

TannerRogalsky / punchdrunk

An attempt to replicate the LÖVE API in the browser using moonshine.
http://tannerrogalsky.com/punchdrunk/
MIT License
81 stars 10 forks source link

missing module #39

Closed SiENcE closed 10 years ago

SiENcE commented 10 years ago

Issue when executing: "Local Npm module "grunt-mocha-phantomjs" not found. Is it installed?"

Solution, add this to install instructions: npm install grunt-mocha-phantomjs

TannerRogalsky commented 10 years ago

That module is already in package.json: https://github.com/TannerRogalsky/punchdrunk/blob/master/package.json#L29

Are you sure you ran npm install?

SiENcE commented 10 years ago

Yep. I have updated punchdrunk from head and wanted to start punchdrunk. Than this error came up.

TannerRogalsky commented 10 years ago

I can't reproduce this behaviour. grunt-mocha-phantomjs@0.4.3 is installed locally in this project when I run the install command on a fresh clone of this repo. Can you delete your node_modules folder and then paste the output from running npm install?

SiENcE commented 10 years ago

The output is to large to paste.

After doing this i get this when starting grunt.

$ grunt Loading "Gruntfile.coffee" tasks...ERROR

Error: Cannot find module 'moonshine/bin/commands/distil.js' Warning: Task "distil_game" not found. Use --force to continue.

Aborted due to warnings.

TannerRogalsky commented 10 years ago

Looks like you're missing a different module now (the moonshine module). What's your dev environment? This works for me under Windows PowerShell on Windows 7. And I really need to see the output from npm install after you delete node_modules. If you could just put it in a gist, that would be very helpful in debugging this.

SiENcE commented 10 years ago

I use Win7 64bit + git-shell. I deleted it again and did npm install and now everything works. Might be a download issue.

This was in the npm-debug.log of the attempt before.

16700 silly gunzTarPerm extractEntry lib/nodes/doctype.js 16701 silly gunzTarPerm modified mode [ 'lib/nodes/doctype.js', 438, 420 ] 16702 silly gunzTarPerm extractEntry lib/nodes/case.js 16703 silly gunzTarPerm modified mode [ 'lib/nodes/case.js', 438, 420 ] 16704 error error rolling back Error: ENOTEMPTY, rmdir 'D:\punchdrunk\node_modules\moonshine\node_modules\express\node_modules\connect\lib\middleware' 16704 error error rolling back moonshine@0.0.11 { [Error: ENOTEMPTY, rmdir 'D:\punchdrunk\node_modules\moonshine\node_modules\express\node_modules\connect\lib\middleware'] 16704 error error rolling back errno: 53, 16704 error error rolling back code: 'ENOTEMPTY', 16704 error error rolling back path: 'D:\punchdrunk\node_modules\moonshine\node_modules\express\node_modules\connect\lib\middleware' } 16705 error Error: ENOTEMPTY, rmdir 'C:\Users\xxxxxx\AppData\Roaming\npm-cache\socket.io-client\0.9.11\package\test' 16706 error If you need help, you may report this log at: 16706 error http://github.com/isaacs/npm/issues 16706 error or email it to: 16706 error npm-@googlegroups.com 16707 error System Windows_NT 6.1.7601 16708 error command "c:\Program Files\nodejs\node.exe" "c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" 16709 error cwd D:\punchdrunk 16710 error node -v v0.10.22 16711 error npm -v 1.3.14 16712 error path C:\Users\xxxxxx\AppData\Roaming\npm-cache\socket.io-client\0.9.11\package\test 16713 error code ENOTEMPTY 16714 error errno 53 16715 verbose exit [ 53, true ]

TannerRogalsky commented 10 years ago

Maybe try deleting your everything in your npm-cache folder (at C:\Users\xxxxxx\AppData\Roaming\npm-cache) and then npm install again.

SiENcE commented 10 years ago

Everything fine now!