ncage (Community Member) asked a question.
We are having issues figuring out exactly how to bundle our application. Initially this is how we bundled our app:
You don't see it in the screenshot but we originally had 3rd party dependency dlls in their too. Support told me to take all 3rd party dependency dlls out (.net core).
Underneath our js folder we had our bundle we build for our application (in debug mode):
It was failing on the pre-scan when looking at our javascript bundle. From what i got from support it was failing because our bundle had 3rd party dependencies.
So what i end up trying is to include all of our raw *.ts, *.vue, & *.js files. Here is what it looks like now:
as you can see underneath our js folder i put all our raw files.
When i upload our this to the servers for a static scan:
As you can see when i click on "review modules" there are are no files listed (No supporting files or PDB files) so i'm a little confused. How do we need to package are javascript (*.vue, *.ts, *.js) assets so they are scanned correctly?
.png){kind=logo}
Just an update. I see in the docs where it recommends packaging your javascript/typescript/vue seperately from your .net build:
When you submit .NET applications that use TypeScript for analysis, package the TypeScript source files separately from the .NET application.
So for a test I'm just uploading our front end assets (javascript/typescript/vue) & didn't include our .net portion of our application. I also forgot to include our `package-lock.json` so i've included that. Its scanning currently and, as of yet, i don't see any differences but i will let you know when the scan is complete.
Hello Ncage,
Were you scan javascript completely?
I am currently having issues scan mine.