socket.io dependency needs version bump
See original GitHub issueIssue details
When I run yarn install
to install something with the latest browser-sync as a dependency, I get this output:
warning browser-sync > socket.io > engine.io > uws@9.14.0: stop using this version
I noticed browser-sync is currently locked to version 2.0.4 of socket.io. I also noticed that socket.io v2.1.0 seems to have made a change that would get rid of this warning. So please update the socket.io dependency to v2.1.0.
Please specify which version of Browsersync, node and npm you’re running
- Browsersync [ 2.24.4 ]
- Node [ 8.9.4 ]
- Npm [ 5.6.0 ]
- Yarn [ 1.6.0 ]
Affected platforms
I am on macOS but I’m sure this applies to any platform.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Migrating from 3.x to 4.0 - Socket.IO
0 release adds quite a lot of new features, which are detailed below, but it also contains a few API breaking changes (hence...
Read more >Dependencies are outdated and there are vulnerabilities #3709
You want to: report a bug request a feature Current behaviour npm outdated reports many dependencies as out of date: C:\ws\socketio>npm ...
Read more >socket.io - Yarn
Socket.IO enables real-time bidirectional event-based communication. It consists of: a Node.js server (this repository); a Javascript client library for the ...
Read more >socket.io - npm
node.js realtime framework server. Latest version: 4.5.4, last published: a month ago. Start using socket.io in your project by running `npm ...
Read more >Socket.io, migrating from 2.x to 3.0 - General - Node-RED Forum
I suspect that having 2 different socket io dependencies of version 2 and 3 on the same server and client will probably not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@garrettw The fix is in place, it’s just the jump to Mocha 4 that threw me off (needing the
--exit
flag) - I hope to get the release done this evening 😃Any news @shakyShane? The
--exit
is recommended since mocha v4.0:I tried the latest version of mocha (5.2) which works if the
--exit
flag is present.