sonar-properties

You can generate a SonarQube configuration for a Vue.js project by providing the application name, allowing the generator to auto-detect Vitest or Jest from package.json and map coverage paths into sonar-project.properties.

Auto-detection for Vitest and Jest coverage paths works by reading the package.json file to identify the active test framework, then dynamically configuring the sonar-project.properties coverage report locations based on that specific framework.

Yes, you can automatically exclude specific files like services, routers, interfaces, and constants from SonarQube coverage. The generator builds exclusions dynamically based on common project structures alongside the src/main.ts file.

Yes, the generated sonar-project.properties file configures SCM and encoding settings by enforcing UTF-8 encoding, setting git as the SCM provider, and enabling the QC wait setting for the Vue.js project analysis.

To start generating SonarQube properties for your TypeScript project, you only need to provide the application_name config. The generator handles test framework detection, projectKey derivation, and coverage exclusions automatically.

A limitation when mapping coverage paths for Vue.js projects in SonarQube is that the generator relies on predefined common project structures like src/main.ts and specific directories, meaning non-standard file layouts may require manual adjustments after generation.