Polly.js – Record, replay, and stub HTTP interactions
netflix.github.io
Polly.js – Record, replay, and stub HTTP interactions
1–10 of 11 posts
Re: Polly.js – Record, replay, and stub HTTP interactions
#2Re: Polly.js – Record, replay, and stub HTTP interactions
#3What is surprising is that Netflix is pushing out JavaScript, and not TypeScript, related projects in 2024.
https://github.com/Netflix/pollyjs/commit/281115d359ee0da5e0...
Re: Polly.js – Record, replay, and stub HTTP interactions
#4Re: Polly.js – Record, replay, and stub HTTP interactions
#5What is surprising is that Netflix is pushing out JavaScript, and not TypeScript, related projects in 2024.
Re: Polly.js – Record, replay, and stub HTTP interactions
#6What is the benefit of this over MSW ( https://mswjs.io/ )
- 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!
Re: Polly.js – Record, replay, and stub HTTP interactions
#7What is surprising is that Netflix is pushing out JavaScript, and not TypeScript, related projects in 2024.
Re: Polly.js – Record, replay, and stub HTTP interactions
#8Re: Polly.js – Record, replay, and stub HTTP interactions
#9Could 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.