Prioritize - NPM Project Analysis is Failing
Problem
Error during Prioritize scan
Solution
Configuration verification:
All dependencies resolutions except NPM are disabled - resolveAllDependencies=false
includes=**/*.js
updateType=OVERRIDE
Verify the following NPM part of configuration:
a) npm.resolveDependencies=true
b) npm.resolveLockFile=false (true by default)
c) npm.resolveAdditionalDependencies=false
d) npm.includeDevDependencies=true
e) npm.ignoreNpmLsErrors=false
f) npm.identifyByNameAndVersion=false
g) npm.yarnProject=false
5. Verify ‘npm ls’ completed successfully on the scanned project
6. Verify the appPath points on the package.json
When opening a ticket for Mend Support, please attach the following:
Unified Agent debug log – debug log located under Mend folder next to the wss-unified-agent.jar
Additional option is to add ‘-logLevel’ debug to the execution command and attach the output to the support ticketPrioritize debug folder. In order to enable Prioritize log for specific scan - add ‘-viaDebug true’ to the execution command. Prioritize debug folder will be located under ‘tmp’ folder. Exact link printed at the end of the Unified Agent log and will be like: /tmp/whitesource123456789012345/
Limitations
Currently Prioritize is not supported in the following scenarios:
As a part of GitLab CI
As a part of the Azure DevOps Integration
For analyzing front-end projects