fix: scanoss bundling

[sdirix]

What it does

scanoss depends on node-fetch <3. node-fetch in that version fails their instance checks, as it relies on constructor/class names which are removed by the backend bundling.

Customizes the webpack configurations to keep the class name for 'AbortSignal' as this is the one failing the check.

How to test

Build the Browser and/or Electron production builds and make sure that SCANOSS keeps working.

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

[tsmaeder]

From the code, this looks good to me. @sdirix were you able to test this locally? Also, we should remove the "patch" this PR applies to the generated webpack config when we consume a version that contains eclipse-theia/theia#14650

[sdirix]

Also, we should remove the "patch" this PR applies to the generated webpack config when we consume a version that contains eclipse-theia/theia#14650

We can only remove this patch for the Browser variant. In the Electron variant we already overwrote the TerserPlugin, so our additional customization must still be kept.

From the code, this looks good to me. @sdirix were you able to test this locally?

Yes I tested the production variants of Browser, Electron and packaged Electron (Linux AppImage) and all of them worked for me.

[jfaltermeier]

LGTM, AppImage and Docker Container work for me

[JonasHelming]

@jfaltermeier We should trigger a patch release now

[sdirix]

@jfaltermeier @JonasHelming, @tsmaeder is encountering another issue. Maybe it's because he is on a Windows machine. Let's quickly verify before we do the release. See here.

[sdirix]

The Windows issue was fixed here: eclipse-theia/theia#14653