If you've been searching for a way to mock HTTP requests in your browser, you've likely come across both tweak and Requestly. Both tools let you intercept and modify network requests without touching your backend, but they approach the problem differently. This post breaks down what each tool does well and when you should reach for one over the other.
Modern browsers have advanced development toolkits allowing HTTP request inspection in detail. With the recent Chrome 111 release users are now able to override response headers directly in the network panel. This means tools like browser extension are not needed to accomplish simple use cases. In this article we explore the current possibilities and limitations of one of the newest Chrome DevTools features.
Keyboard shortcuts are an essential tool for web developers, as they can help speed up common tasks and improve efficiency in the development process. In modern browsers such as Google Chrome and Mozilla Firefox, keyboard shortcuts can be especially helpful for debugging, as they allow developers to quickly access and navigate various development tools without needing to use their mouse or trackpad. We're also looking into why you should give a damn about shortcuts.
During our web development daily activities it's common to poke around the browser to test our applications or replicate weird behaviors, often caused by API calls errors. In this short tutorial you can learn how to override a XHR/Fetch response status code with the tweak browser extension.
Modern browsers have advanced development toolkits allowing developers to inspect and debug their code in detail. This article will go through the options you have to block HTTP requests with modern browsers.
A genuine Chrome browser power user can only reach maximum efficiency using shortcuts. Shortcuts bridge the gap over repetitive tasks that might not be individually super time-consuming. Still, they do add up and crawl up your productivity with time.
Errors handling is part of our work as developers. You can try to ignore them at first, but to offer a good user experience, you don't want your website breaking just because one of the API endpoints decided to give up on you. These days we try to find clever workarounds to run our applications with a graceful degradation strategy. We build software to work in an optimal environment while providing certain fallbacks not to break the experience entirely when there's some disturbance in the system (e.g., lousy network condition, CPU lag, etc.).
In this article, we will understand how to maximize productivity when tackling HTTP requests error handling from a front-end development perspective.
We're always looking for new ways to improve our effectiveness as frontend developers. We want to pick the right tools to get the job done. We want to have a fully equipped browser, to troubleshoot any tricky bug that comes our way.
Browser extensions have been around for a while, making their way into our development workflow in many different shapes. We can think of extensions as development companions.
In this article, we would like to share a few of them, that in our opinion, provide valuable assistance for frontend developers.
There might be a few reasons why we would want to delay an HTTP request:
When I first started my career in the software industry, I began to get familiar with Single-page applications and how they interact with servers, mainly through HTTP requests to retrieve or send data to the end-user. If you're working with the front end, there's a very high chance you found yourself in one (or multiple) of the following scenarios.