Data fetching on the web still sucks

• uWebSockets.js

  32 7,240 8.2 C++

  μWebSockets for Node.js back-ends :metal:

  

I'm currently experimenting with React and WebSockets and they seem to be a perfect fit.

No need to write wrappers for Fetch, network errors and reconnects can be handled on high-level, handlers for each message type can be mounted and unmounted on useEffect hook, all back-end jobs can notify the user in realtime, all session-based client-side data can be updated in realtime (in single or multiple open tabs).

I'm also using uWebSockets.js[0] which is great in terms of API design, stability, and performance. Their benchmarks[1] are just convincing.

[0] https://github.com/uNetworking/uWebSockets.js/

• µWebSockets

  41 16,699 8.6 C++

  Simple, secure & standards compliant web server for the most demanding of applications

  

[1] https://github.com/uNetworking/uWebSockets/tree/master/bench...

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• fetch-progress-indicators

  2 324 0.0 HTML

  Progress indicators/bars using Streams, Service Workers, and Fetch APIs

I didn't see "show download progress" as one of the needs. I remember seeing complaints about the fetch api not exposing an easy way to do that. Issues like this one seem to remain: https://github.com/AnthumChris/fetch-progress-indicators/iss...

Suggest a related project