10.7 | Analyzing source code | Scanners | SonarScanner for NPM | Using the scanner
Using the SonarScanner for NPM
You can start the SonarScanner for NPM and thus, integrate it into your CI or build pipeline, in the following ways:
- From the command line.
A global mode installation of the scanner is required. - From the command line with npx.
No scanner installation is required. - By adding the analysis step to your build files.
The scanner must be added to the project’s devDependencies.
You can pass analysis parameters in the command line and in the analysis step coded in JS. In addition, the SonarScanner for NPM gets analysis parameters from different other sources: see Configuring the project analysis parameters. To get started, you must configure at a minimum the SonarQube server host URL and the token used to connect to the server.
The SonarScanners run on code that is checked out. See Verifying the code checkout step of your build.
Starting the scanner from the command line
- Make sure the scanner is installed in global mode: see Installing the scanner in global mode.
- Use the
sonar-scanner
command to start the analysis.
To pass analysis parameters in the command line, use the standard-Dsonar.xxx=yyy
syntax.
Example:
Starting the scanner from the command line with npx
- Use the
npx sonarqube-scanner
command to start the analysis.
To pass analysis parameters in the command line, use the standard-Dsonar.xxx=yyy
syntax.
Example:
Adding the analysis step to your build files
- Make sure the scanner is installed in your project’s devDependencies: see Adding the scanner to your project devDependencies.
- Code the analysis step in JS in your build files, as shown in the example below.
Where the syntax is as follows:
- parameters (format: Map)
- serverUrl (format: String; optional): The URL of the SonarQube server. Defaults to the value of the SonarCloud URL (
sonar.scanner.cloudUrl
property). - token (format: String; optional): The token used to connect to the SonarQube server or SonarCloud. Empty by default.
- options (format: Map; optional): Used to pass extra parameters for the analysis. See Configuring the analysis parameters for more details.
- serverUrl (format: String; optional): The URL of the SonarQube server. Defaults to the value of the SonarCloud URL (
- callback (format: Function; optional): Callback (the execution of the analysis is asynchronous).
Was this page helpful?