10 comments

[ 5.7 ms ] story [ 37.2 ms ] thread
What is surprising is that Netflix is pushing out JavaScript, and not TypeScript, related projects in 2024.
I'm pretty comfortable with JavaScript, Python and C#. You would think I would love TypeScript, but I specifically mainly use JS when its native to the browser, I hate the nightmare that is maintaining JS tools and packages. I can understand why someone might want to avoid the ceremony of setting up a JS project and just use as much OOTB as possible.
They are using tsc though. It’s all type-checked. In my experience using tsc on JavaScript files is a good experience. But you don’t get the full feature set.
What is the benefit of this over MSW (https://mswjs.io/)
You can mock with service workers in real time and deploy them globally as edge workers without ever leaving your browser or learning non-standard APIs:

- <https://sw.rt.ht/?> (worker inside https://RTCode.io)

- https://sw.rt.ht/ (deployed to https://RTEdge.net)

Editor: Everything is real-time! Try editing things. (You can intercept requests to other domains by using io:host=* on the worker.)

Editor/Edge: This uses standard web platform APIs! In addition, KV storage (in-editor/edge-deployed) is ready, object storage, and more is in the works!

Could I use this library to implement offline support for an API (for example htmx requests)? I'm imagine I could capture requests in the web worker to add in offline logic.