-
Notifications
You must be signed in to change notification settings - Fork 117
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
createPage does not callback #112
Comments
+1 |
+1 @bengfarrell This is the problem, indeed. |
yup: #104 |
Guys, I am using Before running it, you should make sure that the supported version of socket.io (0.9.16 works for me) is installed in node_modules. Then run it to generate npm-shrinkwrap.json: $ npm shrinkwrap --dev When a team member downloads your repo, there is nothing extra she/he should do, just $ npm install But during development, you should regenerate the npm-shrinkwrap.json if you add/remove/update-to-new-version-of a module. I hope this will be helpful for you. |
@alexscheelmeyer Can we get this change into the npm package repository? It is really annoying to do it manually all the time. |
+1 |
It used to be that my project using this node-phantom package worked. Now it doesn't. CreatePage now no longer calls back.
It would seem that the difference is that Socket.IO was updated past 1.0. If I force an npm install of socket.io 0.9.16, everything seems to work.
However, the package.json specifies >=0.9.6 and I end up with 1.0.6, which seems to have some issues with this project...mainly that I don't seem to be getting socket.on('res') messages.
The text was updated successfully, but these errors were encountered: