-
Notifications
You must be signed in to change notification settings - Fork 177
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
Setup broadcaster with socket.io #66
Comments
pusher is a hard dependency for some reason. doing a simple npm install pusher should do the trick |
I don't use pusher dependency, because i set up my Echo with socket. But thanks I figured out by creating a webpack.config.js where i skipped pusher-js. |
ah that was the other option indeed 👍 |
It does @happyDemon , i did add also pusher-js and webpack passed. can you tell me if i need to run laravel-echo-server each times i'd like to communicate my socket, also do i need socketIO configuration stuff in the client. |
This should do it: You do have to keep the node server running to listen to/send events. |
@mealinks can i have an example for how you skip the pusher-js? many thanks |
Hey @martingg88 here is a relative issue #52 |
Closing this issue because it's already solved, old or not relevant anymore. Feel free to reply if you're still experiencing this issue. |
can someone help, I have this same issue |
Hi,
I followed the basic configuration of WebSocket given within the docs (driver: Redis, socket.io), but each times i run
gulp
, I got the error below :Hope someone can help me to figure out this problem, knwoing that i didn't do any setup with pusher-js.
The text was updated successfully, but these errors were encountered: