-
Notifications
You must be signed in to change notification settings - Fork 4
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
Game won't run #19
Comments
Using node.js version 0.6.14 on Windows. No issue on my end. Update to 0.6.14, then check your issues. |
Have you gotten it working on your machine before? |
fualkner: Please check your node.js build (we use 0.6.14) and make sure you have all dependencies installed, the package.js file is currently out of date and will be updated when I push the new server core sometime this weekend. Current Dependencies:
|
Just downloaded the Node.js installer (.msi) and completed that; now could you instruct me on which commands to use? I'm quite new at JS. Thanks, guys. |
"npm start" is an alias for "node app.js" basically, so just type "node app.js" If you get an issue, run "node -v" and report your version. |
I have v0.6.14. I didn't uninstall the previous version; would that be a stumbling block? Game still isn't loading, previous versions did work on my machine. npm-debug: https://gist.github.com/2270894 Thanks for the help, gents. |
Try pulling in the latest changes to the repo and let me know the results! |
I got several "RedisError: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED". localhost:3000 hangs and eventually (sometimes) leads to "Loading Cemetery Mania..." and then a message telling me to go to Facebook. I have a tab open with Facebook, does it mean something else? |
You need to be running an instance of redis in order for the server to run. Also, the game is tightly integrated with facebook but |
Tried node app.js and npm start. Did both the install commands. Is the program currently not operational?
Here's the npm-debug file:
info it worked if it ends with ok
verbose cli [ 'C:\Program Files (x86)\nodejs\node.exe',
verbose cli 'C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js',
verbose cli 'start' ]
info using [email protected]
info using [email protected]
verbose C:\Program Files (x86)\nodejs\node.exe node symlink
verbose config file C:\Users\Patrick.npmrc
verbose config file C:\Program Files (x86)\nodejs\etc\npmrc
verbose config file C:\Program Files (x86)\nodejs\node_modules\npm\npmrc
verbose mkdir done: C:\Users\Patrick\AppData\Roaming\npm 755
verbose caching C:\Users\Patrick\Documents\Javascript\CemeteryMania\package.json
verbose loadDefaults [email protected]
verbose run-script [ 'prestart', 'start', 'poststart' ]
info prestart [email protected]
info start [email protected]
verbose unsafe-perm in lifecycle true
silly exec cmd "/c" "node app.js"
silly spawning [ 'cmd',
silly spawning [ '/c', 'node app.js' ],
silly spawning 'C:\Users\Patrick\Documents\Javascript\CemeteryMania' ]
info [email protected] Failed to exec start script
ERR! [email protected] start:
node app.js
ERR!
cmd "/c" "node app.js"
failed with 1ERR!
ERR! Failed at the [email protected] start script.
ERR! This is most likely a problem with the CemeteryMania package,
ERR! not with npm itself.
ERR! Tell the author that this fails on your system:
ERR! node app.js
ERR! You can get their info via:
ERR! npm owner ls CemeteryMania
ERR! There is likely additional logging output above.
ERR!
ERR! System Windows_NT 6.1.7600
ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "start"
ERR! cwd C:\Users\Patrick\Documents\Javascript\CemeteryMania
ERR! node -v v0.6.12
ERR! npm -v 1.1.4
ERR! code ELIFECYCLE
ERR! message [email protected] start:
node app.js
ERR! message
cmd "/c" "node app.js"
failed with 1ERR! errno {}
verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: