Requestly VS flipper

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

Definitely switch to VS Code! I personally don't use the built in VS Code debugger, but check out Flipper as another option. It's got a lot of great tools and plugins for debugging. The Layout Inspector will be what you are looking for if you want to inspect the styling specifically.

I use Flipper with its Layout Inspector plugin

Also no folder show on sources filesystem (in Hermes Debugger) as described here: https://github.com/facebook/flipper/issues/4530

Very useful and beautiful and simply , my suggestion is to use this Flipper

You may also want to look into custom Flipper plugins to instrument your app.

Some development tools for the web are similar (Chrome debugger, mostly) to those for React Native, but other aspects are very different (working with the metro bundler, using Flipper, AsyncStorage debugging, more). Some techniques developers will use are the same (breakpoints and console logging), but others are different (knowing when to restart the packager vs reinstall the app on device).

from the GitHub, and has existed under the name flipper since mid 2018

It's not possible to use a browser to debug a JSI app, use Flipper (for android Flipper also has SQLite Database explorer).

Try to debug it with adb logcat or Android Studio or Flipper you'll find the error why is crashing :)