The UpgradeJS Blog

Welcome to the third installment in our series of blog posts on SonarQube!

In the first chapter, we guided you through the basic configuration of a local SonarQube instance, while in the second chapter, we demonstrated how to set up SonarQube and your application to display unit and end-to-end test data.

In this third chapter, we’ll explore the integration of SonarLint with WebStorm IDE to help you catch issues early on in the development process.

SonarQube is an open-source platform developed by SonarSource that provides continuous inspection of code quality through static code analysis.

There are two ways to set up SonarQube analysis - you can select from the cloud solution (sonarcloud) or install a SonarQube instance on your machine or a remote server. In the first chapter we set up a local SonarQube instance and ran the analysis for a simple JavaScript application

In this chapter, we will continue to work with the same application and add more features to it.

SonarQube is an open-source platform developed by SonarSource that provides continuous inspection of code quality through static code analysis.

There are two ways to set up SonarQube analysis - you can select from the cloud solution (sonarcloud) or install a SonarQube instance on your machine or a remote server. Today we will cover setting up a local SonarQube instance to analyze your code.

When upgrading, or paying off tech debt for an application it is important to note that each case requires a distinct strategy. In this experiment, we will explore how the investigation process can be carried out on Express using es6-plato.

Node.js has always been an essential part of the tech stack for many companies and developers. And here at OmbuLabs and UpgradeJS we use it too, due to its efficiency, scalability, and the robust ecosystem it provides.

Recently, the Node.js team released version 20, bringing with it a host of new features and improvements. In this post, we’ll highlight some notable changes and explain why and how to upgrade to Node.js 20.x.

In this article, we’ll cover essential steps, from backing up data to performing the upgrade of your servers, to ensure a successful upgrade of Node.js. These steps can be applied to any version, whether you’re moving between older versions or upgrading to the latest stable release.

By following these steps, you can avoid potential issues, such as data loss or compatibility problems, and ensure a smooth process.

As the upgrade team, one of our most significant challenges is the initial setup of each project, as many of the tools we utilize for inspection need distinct and customized configurations. This is due to the countless methods in which JavaScript/TypeScript projects can be constructed.

In today’s demonstration, we will introduce you to our new open source project called plugin-preloader and show you how you can use it to simplify your workflow if you encounter similar issues as we do.

In this blog post, I initially intended to discuss upgrading React Native applications using the “backwards-compatible” approach. However, I discovered an opportunity to explore another interesting topic: An upgrade regenerating the project.

Join me as we dive into a case study where I successfully upgrade a React Native iOS-targeted application from version 0.59 all the way to the latest version, 0.71!

At OmbuLabs and UpgradeJS we love using React to create dynamic and scalable user interfaces on the front-end of web, mobile, and desktop applications.

With the release of React v18.0, several new features and enhancements have been added that can improve the development experience and boost the performance of React applications.

In this post, we will provide a guide to upgrading your React application from version 16.x to version 18.x, so that you can take advantage of the latest features and improvements.

My team and I were upgrading an OSS project for research purposes, and this blog was written after the actual upgrade was done. Here we will highlight why the step of inspecting the application with SonarQube-like tool is essential and what we missed because we should have checked it during the upgrade project.

When we test our applications, it’s often useful to use more than one tool or framework for different kinds of tests.

For example, in a Backend-for-Frontend (BFF) application, we may have end-to-end (e2e) tests and unit tests. We might use a tool like Cypress for e2e testing and Jest for unit testing.

Each of these tools can produce a test coverage report, but wouldn’t it be nice to be able to combine all our test coverage data into one report? With IstanbulJS, we can!

In this article, I’ll show you how.

In the fast-paced world of software development, keeping track of dependencies and ensuring they are compatible with the latest version of Node can be a daunting task. This is where depngn comes in - a powerful CLI tool designed to help developers determine if their dependencies support a specific version of Node.