sidekick VS Requestly

With our current setup, we got in-depth error information from our backend apps. In further chapters, we will be bringing Sidekick’s tracepoint (non-breaking breakpoint) feature to Cypress that will allow us to define tests based on state and stack information of our backend. Right now, we are also working on a Cypress plugin that will make using Sidekick Actions within Cypress as easy as it gets, and your support and feedback will guide us through our road. After Cypress, supporting other test frameworks is on our roadmap. You can find us at Discord or contact us via our website https://runsidekick.com if you want to participate or become a part of our community

View on GitHub

Sidekick is an open-source live application debugger that lets you troubleshoot your applications while they keep on running. It is like Chrome DevTools for your and built for everyone who needs extra information from their applications.

Sidekick is an open source live application debugger that comes with many built-in features to make data collection both easier and more efficient. Collecting snapshots and generating logs from running applications are powerful for learning how your code works as long as you collect the data you need.

Please let us know your invaluable ideas because they will guide us on our path to discovering the future of application observability. You can get in touch with us through Github, Twitter, and join our Discord community.

Sidekick Open Source Github Repository: https://github.com/runsidekick/sidekick (don't forget to give us a ⭐)

Requestly- Makes frontend development cycle 10x faster with API Client, Mock Server, Intercept & Modify HTTP Requests and Session Replays.

[1]: https://github.com/requestly/requestly/

If you want to intercept and modify a incoming json response for some specific url pattern, would a service worker be a good way to do so?

To illustrate, assume I frequently browse example.com and want to trick my browser into thinking that I have "favorited" every post. It's trivial to write a for loop that iterates over response.json and sets `is_favorite = true`. But it's not as clear to me where this script should ideally live in order to have the logic always executed before the response is made available to the site.

Your comment made me think about whether I can replace my overkill solution (https://requestly.io/) with something lightweight.

If you prefer open-source there is Requestly and Toolkit.

If you don't know Requestly, It is an open-source Chrome/Firefox/Edge extension to intercept & modify HTTP requests & responses. One of the popular features is to modify HTTP headers. We also offer workspaces for easy collaboration between team members.

Hey, open-source community, This is Sachin, One of the core maintainers of Requestly - An open-source alternative to Charles Proxy & Telerik Fiddler. In case you don’t know about Charles Proxy & Fiddler, both of them are two decades-old products used widely to Inspect & Modify HTTP traffic in web & mobile apps.

In /etc/hosts file you put only IP addresses and hostnames, i.e. 127.0.0.1 cdn.cloudflare.steamstatic.com. Then you have to set up a web server on localhost port 80 and put your image at http://localhost/steamcommunity/public/images/apps/753/1d0167575d746dadea7706685c0f3c01c8aeb6d8.jpg as well as other files from https://cdn.cloudflare.steamstatic.com. You also have to keep the URLs updated when they change upstream. It's not worth it. Better use a local proxy server like mitmproxy or requestly.

Requestly founder here. You are essentially looking for Requestly - A Chrome/Firefox browser extension to Intercept & Modify HTTP requests. Using Requestly you can actually do the following things

For development/Debugging: 1. VSCode - Got used to the key bindings and integrated terminal, so now it's really hard to switch 2. Requestly - For easily setting up local debugging environments. I am less of a UI guy, so this allows me to use the live UI of a deployed site, and redirect whichever request I want to play with to my local server. 3. Wireshark - To better understand a network protocol.

[0]: https://requestly.io