Use the latest `ws`?
See original GitHub issueIt looks like ws is two major revs ahead of what express-ws lists in its dependencies. Perhaps worth moving to it?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:11
Top Results From Across the Web
ws: a Node.js WebSocket library - GitHub
ws is a simple to use, blazing fast, and thoroughly tested WebSocket client and server implementation. Passes the quite extensive Autobahn test suite:...
Read more >USA TODAY - Today's Breaking News, US & World News
USA TODAY delivers current national and local news, sports, entertainment, finance, technology, and more through award-winning journalism, photos, ...
Read more >CNN - Breaking News, Latest News and Videos
View the latest news and breaking news today for U.S., world, weather, entertainment, politics and health at CNN.com.
Read more >NBC News - Breaking News & Top Stories - Latest World, US ...
Go to NBCNews.com for breaking news, videos, and the latest top stories in world news, business, politics, health and pop culture.
Read more >Associated Press News: Breaking News | Latest News Today
Stay informed and read the latest news today from The Associated Press, the definitive source for independent journalism from every corner of the...
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 Free
Top 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

As with @AuspeXeu I’ve now just dropped my use of this module. In case it helps, here’s the commit in my project that made the change: https://github.com/danfuzz/bayou/pull/466/commits/4ed5569049c138e0e26fb55b1c069e2be8c0a1a6
BTW, one thing to watch out for is that my change makes it so that
expressisn’t involved at all in websocket requests. This means that any route intercepters / middleware you might have installed — notably logging — won’t get invoked.