which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)
sonar-scanner-npm ^4.2.1
how is SonarQube deployed: zip, Docker, Helm
N/A
what are you trying to achieve
N/A
what have you tried so far to achieve this
N/A
Version 4.2.7 of sonar-scanner-npm changes the output directory of all the compiled files from sonarqube-scanner/build/src/*.js to sonarqube-scanner/src/*.js.
In enterprise settings, where they may be importing things like scanner-cli.js or request.js to perform org-specific actions pre-download, minor changes like this can have…unwanted effects. Please let me know if you need more information, thank you.
@sc1 , thank you for the report - and raising the issue that it was not clear where to open issues about the scanner. We took some actions to make it explicit in the documentation of the package.
About your breaking change report, the physical location of the artifacts hosted by an npm package is not contractual. Even the entry point of the package is not. The only thing that is contractual is that the main - and exports - directives exposes a public API that does not include breaking changes.
I know that it was quite common in the past - and still is - to import some modules from their physical location inside a package, but it was never guaranteed to work (because of the location being non-contractual), and it is now totally forbidden by Node.js ECMAScript modules specification.