Home Developer Monorepo with Static Code Analysis

Monorepo with Static Code Analysis

Author

Date

Category

Monorepo is short for monorepository. With it, code for many projects is stored in the same repository. I like to use monorepo for NodeJS and React projects but sometimes it’s difficult to use monorepo when performing static code analysis (SCA), particularly when it comes to code coverage and code patterns. However, Codacy’s tool helps with this. Let me show you how below:

Code Coverage

Because many projects are stored in the same repository, many coding languages co-exist. Therefore, code coverage (checking code for errors) becomes complicated.  

A tool that enables reports in multiple programming languages is helpful to address these concerns. With Codacy, I receive backend and frontend reports for each language in each repo.  The weight is also calculated.  

You can see the documentation here and an excerpt below:

Code Patterns

I also worry about code patterns when using monorepos with static code analysis. Linting tools detect code patterns. However, these tend to be specific to coding languages. With multiple projects in multiple coding languages things can get tricky.

Example with ESLint

We’ll focus on ESLint in our example as it is a top linting tool for JavaScript developers with many useful plugins.  Although ESLint alone doesn’t solve for issues of having two different projects in the same repository, there is a work around:

Solution

In the src folder of the project create a client and server folder.  This is where it makes sense to have the .eslintrs.js file. In this, common rules can be set (or left empty).  

monorepo

Then, inside each client or server folder, an additional .eslintr.js, extending the src file can be added. This overrides the previously defined rules.

Locally seems to be going as expected. Now, to Codacy. Under the “Code Patterns” tab, I chose “Configuration File” instead of the Rules from the UI.

We get the same, expected results:

As you can see, with these techniques (and some help from Codacy) monorepo should no longer be an obstacle with static code analysis.

Want more from Helio, a Solutions Engineer at Codacy? Follow him on twitter.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Subscribe to our newsletter

To be updated with all the latest news, offers and special announcements.

Recent posts

Static Code Analysis: client-side tools integration with Codacy

Testing and analyzing your code is one of the most important parts of your software development process. With Codacy, you can...

Open salary calculator: our commitment to transparency and fairness

Here at Codacy, we are committed to being a fully transparent company. So back in 2019, we launched our open salary...

How Vevo uses Codacy to replace legacy systems while guaranteeing code coverage

As the tech world keeps evolving, having legacy systems is a certainty, especially for organizations that have been around for decades....

December Product Update 🚀

Hi there 👋, With 2021 in the rearview mirror, we can now focus on making 2022 an incredible...

How Loft uses Pulse to measure Engineering health

Customer story about how Loft uses Pulse to measure Engineering health. Estimated reading time: 5 minutes. About Loft