You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using the scanTargets option and specifying either package-lock.json files OR an ANT glob pattern like 'src/**/.js', the scan works great. However, if I specify both the package-lock.json files AND the ANT glob, then only the ANT glob results appear in the scan. Moving the ANT glob to different positions in the list did not change the behavior.
To Reproduce
For an npm project wrapped with Gradle where the src directory contains node_modules instead of a package-lock.json file, a scanTargets option like the following produces results for only the ANT glob pattern.
Describe the bug
When using the scanTargets option and specifying either package-lock.json files OR an ANT glob pattern like 'src/**/.js', the scan works great. However, if I specify both the package-lock.json files AND the ANT glob, then only the ANT glob results appear in the scan. Moving the ANT glob to different positions in the list did not change the behavior.
To Reproduce
For an npm project wrapped with Gradle where the src directory contains node_modules instead of a package-lock.json file, a scanTargets option like the following produces results for only the ANT glob pattern.
Expected behavior
Scan across all targets in the scanTargets list.
Screenshots
n/a
Desktop (please complete the following information):
Additional context
n/a
The text was updated successfully, but these errors were encountered: