Should I exclude the /dist folder from sonarQube scan

SonarQube :, Scanner:

I have an angular project to scan and scan works perfectly fine. But should I exclude /dist folder from scan when running it ? Or do you think its a good practice to fix the build generated /dist folder files like main.js and vendor.js ??


Welcome to the community!

SO tells me that dist is where minified production versions of libs and code go. So you should exclude it. Otherwise, it’ll be a painful experience with all the issues in a library or file reported on the same unreadable line. Plus since you’re presumably analyzing the contents of src any issues raised on code in dist should be duplicates.