In the modern web, code splitting is essential. You want to keep your app slim, with a small bundle size, while having “First Contentful Paint” as fast as possible. But what happens when a dynamic module fails to fetch? In this short article, we’ll see how to overcome such difficulties.
At Sentry, we practice continuous delivery, which means that code can be released as soon as it’s merged into the main branch. This allows us to iterate quickly on our product, making new features, bug fixes, configuration changes, and experiments available in production as frequently as possible. We merge over 700 pull requests a month.
You can hardly even talk about web development without mentioning JavaScript. Because of its popularity, JavaScript has given birth to several frameworks and libraries that developers can barely keep up with. This post will discuss two popular JavaScript front-end frameworks and libraries: Svelte vs React and their performance. We’ll determine if Svelte is faster than React or whether Svelte is better than React. We’ll also compare the two to determine which is better for performance.
A good developer knows how to debug code. In fact, most software engineers spend the majority of their time debugging existing code rather than writing new code. When it comes to native app development, debugging and tracking errors during development can be a tricky task. So, in this post, I’ll help you understand how you can debug your React Native applications and also track errors during app development.
Components are reusable bits of code that, most of the time, work and function independently. If you want to be confident that components are working properly, you need to test them. Conveniently, Cypress.io has designed their testing framework to include component testing. This tutorial illustrates the differences between end-to-end (E2E) and component testing, and what to consider when using these methods. Then, you will learn how to use Cypress for component testing.
In this blog post, I’m going to talk about how to integrate Raygun4JS with React at a deeper level than what is provided out-of-the-box. None of these things are needed for Raygun4JS to do its primary job (reporting errors that happen on your website) but provide useful extra value for determining how your React application is performing and what is going wrong when an error occurs.
React Native has become the predominant development framework for cross-platform mobile applications. By interacting with native APIs largely under the hood and requiring only a fractional proportion of platform-specific code, it allows you to build applications for iOS, Android, and the browser using the same declarative JavaScript. But this cross-platform adaptability has its downsides.
Many platforms offer free hosting services for React and other JavaScript frameworks. These frameworks can be used for building single-page applications, which is handy when you need to launch a minimum viable product or a quick proof of concept. Your fellow developers are taking advantage of these tools, and you can too. To narrow down options, I will focus on Firebase in this tutorial.
Monitoring performance in front-end applications is vital. It focuses on the areas of the application users experience. These areas are slow rendering or frame rate, network request errors, and unresponsive user experience. Your application’s users expect the experience of using the application to be fast, responsive, and smooth. In the first article of this series, we discussed some tips for optimizing your React Native application performance.
