nyc VS SonarQube

Compare nyc vs SonarQube and see what are their differences.

nyc

the Istanbul command line interface (by istanbuljs)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
nyc SonarQube
16 65
5,512 8,477
0.4% 1.6%
0.0 9.9
about 1 month ago 7 days ago
JavaScript Java
ISC License GNU Lesser General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

nyc

Posts with mentions or reviews of nyc. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-14.
  • Migrating from Jest to Vitest for your React Application
    16 projects | dev.to | 14 Dec 2023
    Native code coverage via v8 or istanbul.
  • Testing Vue components the right way
    2 projects | dev.to | 6 Feb 2023
    Writing tests is essential, and knowing whether you test all the required cases for your logic is even more critical. The most common testing coverage tool is Istanbul, where you can see how well your tests exercise your code by lines, functions, and branches. Below is an example of how the test coverage report looks in your terminal:
  • Don't target 100% coverage
    3 projects | dev.to | 19 Jan 2023
    Here is a quote from istanbul, one of the most used code coverage tool:
  • Unit testing like a Hacker
    6 projects | dev.to | 28 Oct 2022
    Unit testing framework was already implemented, using Vitest so I started hacking by setting up a coverage provider to explicitly identify the covered/uncovered lines and mentioned this to the maintainer in the comments. I used Istanbul 🇹🇷 for this purpose.
  • Auto-Publish Your Test Coverage Report on GitHub Pages
    2 projects | dev.to | 28 Oct 2022
    Your project probably has a coverage report. If you’re using Jest as your unit test runner, generating a coverage report is embedded in it. It is done with Istanbul under the hood, which generates a nice HTML page presenting the entire project unit test coverage.
  • Dear Linux, Privileged Ports Must Die
    2 projects | news.ycombinator.com | 31 Aug 2022
    > This is a rant written by someone with just enough understanding to be dangerous, but not quite enough wisdom to know why things are still the way they are. Most of the complaints raised are subtly inaccurate.

    Author seems aware of CAP_NET_BIND_SERVICE: https://source.small-tech.org/site.js/app/-/issues/169 and https://github.com/istanbuljs/nyc/issues/1281 – the "side effects" are NodeJS explicitly checking for it, so that's a NodeJS thing and not a Linux thing.

    Yet curiously it's completely unmentioned in this article, in spite that this is probably what started the author's dislike of privileged ports. I guess it was inconvenient as it got in the way of angrily ranting.

  • Comprehensive coverage Jest+Playwright in Next.js TS
    7 projects | dev.to | 29 Jun 2022
    This approach will create two json coverage files, which will be merged together by NYC. Therefore the results will be purely local. If You don't mind using online tools like Codecov or Coveralls for merging data from different tests, then go ahead and use them. They will probably also be more accurate. But if You still want to learn how to get coverage from E2E, then please read through
  • When developing in React, what do you find most frustrating or cumbersome?
    3 projects | /r/reactjs | 14 Mar 2022
    https://istanbul.js.org/ measures how much of your code is covered by tests
  • Production Ready React
    3 projects | dev.to | 18 Jan 2022
    Jest uses a package called Istanbul to provide test coverage metrics such as statement, branch, function, and line coverage so that you can understand and enforce the quality of your test suite, providing more confidence in releases.
  • Aggregating Unit Test Coverage for All Monorepo’s Packages
    3 projects | dev.to | 31 Dec 2021
    So let’s see if nyc (the code coverage generator) can help with that. Hmm… this documentation seems interesting! So basically what I understand from it is that I need to collect all the reports from the different packages and then run the nyc report over it. The flow should be like this:

SonarQube

Posts with mentions or reviews of SonarQube. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-24.

What are some alternatives?

When comparing nyc and SonarQube you can also consider the following projects:

Spotbugs - SpotBugs is FindBugs' successor. A tool for static analysis to look for bugs in Java code.

Checkstyle - Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. By default it supports the Google Java Style Guide and Sun Code Conventions, but is highly configurable. It can be invoked with an ANT task and a command line program.

PMD - An extensible multilanguage static code analyzer.

Error Prone - Catch common Java mistakes as compile-time errors

semgrep - Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.

jest - Delightful JavaScript Testing.

snyk - Snyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli]

infer - A static analyzer for Java, C, C++, and Objective-C

FindBugs - The new home of the FindBugs project

istanbul - Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.

ZAP - The ZAP core project

DependencyCheck - OWASP dependency-check is a software composition analysis utility that detects publicly disclosed vulnerabilities in application dependencies.