Hello, since 4.3.3 the sonar/scan package fails. I noticed the sonarqube-scanner package was reverted to 4.3.2 but not sonar/scan.
I searched in the docs but did not find an answer, what is the difference between sonarqube-scanner and sonar/scan? The documentation mentions mostly @sonar/scan. The npm page shows the same for both but the weekly download statistic displays 10x more downloads for sonarqube-scanner.
Hi,
Welcome to the community!
We’ve released 4.3.4, which fixes the underlying problem.
HTH,
Ann
Hello, Ann
I just realized there are 2 packages referencing the same project.
Are both going to be kept, or should we move from sonarqube-scanner to @sonar/scan?
Thanks!
Hi,
You should use whichever is more convenient for you. sonarqube-scanner is the more conventional invocation from a SonarQube perspective, while @sonar/scan is the NPM-native one. We tried to be thorough.
Ann
Hello @gian1200,
just to add on what @ganncamp already mentioned: we are planning to maintain both (in fact they are the same codebase, just published twice -one for each package name-).
sonarqube-scanner was the legacy package used by many users, so we are not gonna drop that.
Since then, we created the npm @sonar organization, so we are republishing some of our npm packages under that name.
So whatever suits you better 