Update ws dependency to 1.x
See original GitHub issueWhen I try to run heavy loads (many queries consecutively or concurrently) using this library with node 6.6.0, I occasionally run into issues like this one that appear to come from the underlying websockets library. When I shrinkwrap and bump the version of ws up from 0.8.0 to 1.1.1 everything still appears to work for me and the intermittent errors go away.
Is there a reason to stay on ws 0.x or can it be bumped to 1.x? It would be nice to not have to force the version up with shrinkwrap.
I can also try pulling the repo, updating and testing with the new version of ws when I have some time. I assume this is what i need to run:
npm run build
npm run test:node
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to update a dependency in package-lock.json
The easiest way to update it is probably to go into the package-lock.json file as you suggested and modifying the old "version": "#.#....
Read more >Dependency Versions - Spring
Group ID Artifact ID Version
ch.qos.logback logback‑access 1.4.5
ch.qos.logback logback‑classic 1.4.5
ch.qos.logback logback‑core 1.4.5
Read more >Migrating from Axis 1.x - Apache Axis2
In Axis 1.x, the next step is to compile the classes and put them in the Axis.war, and then run the admin client...
Read more >[BUG] Overrides are not updating after running npm install
I have searched the existing issues This issue exists in the latest npm version I am using the latest npm Current Behavior After...
Read more >Installing or updating the latest version of the AWS CLI
This topic describes how to install or update the latest release of the AWS Command Line Interface (AWS CLI) on supported operating systems....
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
There is no specific reason to stick to
ws@v0.8.0
. I’ll try to bump the version in the coming days. If you could send a pull request instead, that would be really cool 😃.Just curious, how many concurrent requests are you executing (even approximately)?
fixed by #74