...
When scanning code generated by Angular 8 (or greater), almost all the methods reported more than once to sealights causing lower coverage and more quality risks.
Cause
Angular 8 changed their its defaults and generates multiple bundled version versions of the code . For like, for example, esm5, esm2015, etc.
They are essentially the same code just in a different format, and then along with the source maps point back to the same code in the original source files.
This in turn creates the duplicate entries in Sealights as they are scanned and reported.
...
This can be done for instance by updating the browserslist value in your configuration.
Update the .slignore file to ignore all the files you don't want
Setting the .slignore with the something similar to the following, depending on the structure of the folders and files:
| Code Block |
|---|
**/esm2015 *-es2015.* |
| Info |
|---|
More details are available in our dedicated article: Using Node.js Agent - Ignoring Files or Folders |
When you want to deploy more than one type
...
For scanning the code, you will not use the
--instrumentForBrowsersoption, as in: Using Node.js Agents - Scanning a build
This should be done on only one of the folders.For instrumenting the code, you will use the
--instrumentForBrowsersas in SeaLights Node.js agent - Scanning and Instrumentation of a Front-End app, but you will also specify the--instrumentationOnlyflag so that a new build scan will not be performed. This should be done on all the folders you want to deploy and capture coverage for.
...