-
Notifications
You must be signed in to change notification settings - Fork 124
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
Starting server (server.js) error #12
Comments
It's a very strange error, Object.assign() is standard in Node.js, but apparently it is not recognized here. What version of Node.js are you using? This doesn't seem to be related to MondoDB in any case! |
Yes, I think so. hm... [root@localhost]# node -v How about this case? hehe T_T |
0.10.48? o_O |
What's the status of this issue? @ultimo5 did you upgrade your Node.js? |
I upgraded, but I still have been faced error. hm... Thank you. |
Thanks for your great job. I am very interesting PQ, wanna run ASAP.
BTW, I faced error when I start server.
[root@localhost]# node server.js
Listening on 8081
/home/neoguru/html/pq_test/js/server/GameServer.js:84
Object.assign(GameServer.db.entities,GameServer.db.client_entities); // me
^
TypeError: Object function Object() { [native code] } has no method 'assign'
at Object.GameServer.readMap (/home/neoguru/html/pq_test/js/server/GameServer.js:84:12)
at Server.io.on.socket.pings (/home/neoguru/html/pq_test/server.js:85:8)
at Server.g (events.js:180:16)
at Server.emit (events.js:92:17)
at net.js:1056:10
at process._tickCallback (node.js:458:13)
at Function.Module.runMain (module.js:499:11)
at startup (node.js:119:16)
at node.js:945:3
I am not fix mongoDB yet. Do I have to set it first?
The text was updated successfully, but these errors were encountered: