-
Notifications
You must be signed in to change notification settings - Fork 29
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
CLI #26
Comments
Oh hi, I am that someone :) |
nodejs/undici#2481 was just merged, which adds the PerformanceTiming API entries needed for this library. So we're getting closer to getting this working in node. |
That's great @ToshB! Any idea of how long it will take of the release of Node with the mentioned features? |
Looks like it was merged into Node two days ago, nodejs/node@05f8172, so it shouldn't be too long. |
And works like a charm too with the nightly build of node 22:
I was gonna try and run this in my golang based speedtest background task as some sort of abomination where I'd use it in chrome via devtools and get the results that way, but I was too busy lately and my current speedtest provider was ok enough. But now I will definitely rebuild this with the cloudflare speedtest. Thanks @ToshB for your effort! |
I tried it too with v22 nightly. Very smooth! Thanks @ToshB! |
Very cool! I am curious to see if the Node speedtest results are comparable to the browser results. I would assume the fetch-implementations in browsers are tuned to the extreme.. Note that there are some speedtest engines which is still not compatible with Node. Specifically the packetloss tests, which requires WebRTC. I was not able to find a working Node implementation of RTCPeerConnection. |
I've tried a browser based speed test in chromium on a raspberrypi where the bandwidth was severely limited for reasons I don't know. The ookla speed test CLI works, but I'm a bit cautious as it collects so much data from the client. This node based speed test seems to be a better alternative. |
Thanks for this project! Are you also planning to add a CLI interface? Someone on HN has already started an implementation, but perhaps you could collab and release it as part of this package.
The text was updated successfully, but these errors were encountered: