Hello Tomás,

Thank you for developing a CLI tool for the Cloudflare speed test.

There is a jitter value presented in https://speed.cloudflare.com/.

Would it be possible to add the Jitter value additional to the existing values?

That would be really helpful to measure the latency-sensitive issues.

Would it be an option to open this library to not just work as a CLI but actually access the functions in my own code?

The code already looks like it's nice and clean and it would just need to export a bunch of stuff.

It would be awesome if this would be considered.

Hi, this is a super cool package. However, right now, it is not built for consumability.
What do you think about making this consumable in third party modules?

Regards
Phil

Hello maintainers of speed-cloudflare-cli,

First and foremost, thank you for creating such a useful tool! I've been utilizing it extensively and I have a couple of feature requests that I believe would make the user experience even better.

Feature Requests:

1. JSON Output Mode: It would be immensely useful if there was an option to get the output in JSON format. This would make it easier to integrate with other tools or scripts, especially for those of us looking to automate or parse the results in different ways. A potential flag could be --json to enable this output mode. speed-cloudflare-cli --json

2. Selective Speed-Mode: While the comprehensive speed checks are great, sometimes we just want to get a quick check or are limited by data. It would be great to have command arguments to selectively check specific file sizes. Something like: speed-cloudflare-cli --speed-mode=25MB

This way, users can choose to only test certain sizes, saving time and bandwidth.

I believe these enhancements would make the tool even more flexible and user-friendly. I look forward to hearing your thoughts on these suggestions!

Node v20.10

(node:4705) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 lookup listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit
    at _addListener (node:events:588:17)
    at TLSSocket.addListener (node:events:606:10)
    at Readable.on (node:internal/streams/readable:1104:35)
    at ClientRequest.<anonymous> (/home/xpaw/.npm/_npx/0b7ac911589d262c/node_modules/speed-cloudflare-cli/cli.js:103:14)
    at ClientRequest.emit (node:events:514:28)
    at tickOnSocket (node:_http_client:834:7)
    at onSocketNT (node:_http_client:897:5)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)

curl https://speed.cloudflare.com/cdn-cgi/trace
fl=136f4
h=speed.cloudflare.com
ip=216.155.55.42
ts=1650455342.373
visit_scheme=https
uag=curl/7.68.0
colo=DUR
http=http/2
loc=AE
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off

The location in https://speed.cloudflare.com/locations is correct, but for some reason it returns Durban (DUR) South Africa instead of DXB for Dubai and the subsequent test fails. I find no contact page for the Speedtest page to contact anyone, but maybe you know someone who can fix it.

Similarly for Johannesburg it returns Frankfurt (FRA). Latency is obviously horrible and the tests are worthless. I believe that there is probably an indexing error in the internal speedtest API which is not fixable from your code because it is not resolving a specific endpoint, but only for display purposes.