-
Notifications
You must be signed in to change notification settings - Fork 1.2k
io undefined after deploy to heroku #766
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
Comments
I'm having the same problem when running grunt serve:dist . I do see that in the code there is a config for serveClient , it gets set to false when production. But even if i set it to true, it doesnt work .. the code work fine with "grunt serve" |
@Tazer ok good I was starting to think I was the only one...hmmm |
Same my end. I'm able to grunt serve however I get the above mentioned io error when deployed to heroku |
What was the solution here, I'm still seeing this, need to set serveClient: true in production. //edit: turns out I was using a higher version of socket.io-client - brought that back to 1.0.6 and it works now! |
Closed due to inactivity |
Hi, just to inform everyone who may face this issue, the problem for me was that newer versions of socket.io-client contain the file within Thus, in
to
and the bundler will then package it correctly into This came up when I remove the |
Hey, I'm having this issue with version 3.8 of the generator. I've tried xeroxoid solution but the socket library is still not getting inside vendor.js. I've also tried installing the bower version and pointing to it, like so: Any idea why? Configuration is: babel, jade, sass, ui-router, bootstrap, ui-bootstrap, mongoose, auth(google, fb), socket.io, gulp, mocha |
Have same issue here... I am working on a project using [email protected] and having issue on gulp serve:dist |
for now @xeroxoid solution worked.. |
to work for both production and development search and update path for |
I went ahead and re-ran the generator with a clean app. just to see if there was anything I could pick-out that I might have changed in the configuration, however, aside from uncommenting the 'Auth' module like so:
grunt build
&grunt buildcontrol:heroku
run normally without errors?However when I load the app in Heroku I still get:
The text was updated successfully, but these errors were encountered: