-
Notifications
You must be signed in to change notification settings - Fork 756
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
npm install -g browser-sync fails with node 4.0.0 #822
Comments
Probably related to socketio/socket.io#2228 |
@Restuta Thanks for the report - we close these types of issues as they are not directly related to Browsersync. They may appear when you install Browsersync, but they would also appear with every other library that uses socket.io too. Leaving it open here would suggest it's a bug with Browsersync itself, so we choose not to. Closing it also does not stop it showing in google searches, so people can still find it if they need to. :) |
@shakyShane thank for clarification. There is a workaround I think with locking down dependencies of socket.io. Not everybody treats github issues as a "bug tracker", but rather as "issue tracker" so by default I think open issue suggest that there is some kind of "issue" with the project, not necessary a bug with the product itself. Otherwise I don't see how we can handle situations like that, some dependency is broken on recent node for all the projects using it, but as the end user I don't want to know which one and why, I just want to use the project and to |
$ npm install -g browser-sync
The text was updated successfully, but these errors were encountered: