fix(build): no audio/video on e2ee call

[Antreesy]

☑️ Resolves

• Fix: Blank screen without audio in desktop app, but working in talk web page #1850
  • Should be a regression from RSPack migration
  • E2EE worker is now loaded with native webpack5 syntax: `new Worker(, import.meta.url)) - but it expects worker to sit on a path relative to E2EE js module
  • Webpack rule (test: /\.worker\.js$/) matched this file and put it through worker-loader, so output path is talk_desktop__dist/assets/[name].js?v=[contenthash]
  • At runtime, webpack native resolution looked for the file at relative path, not in assets, and couldn't find it there.
  • Result: e2ee worker never starts.

🖼️ Screenshots

🏚️ Before	🏡 After
B	A

[ShGKme]

Could you elaborate the solution?

I understand that worker-loader isn't needed in modern setup and likely should be removed anyway.
But I don't understand how the change fixes the bug and why relative path is the issue...

Before/After screenshots are from the web-client, not the Desktop client.
Is it a screenshot of a call with a user from the desktop client?

[Antreesy]

Before/After screenshots are from the web-client, not the Desktop client.
Is it a screenshot of a call with a user from the desktop client?

Yes, incoming video stream is from desktop client

From my understanding, worker is loaded (otherwise we'd see an error), but post and listen messages between worker and e2ee module are incorrectly established

[Antreesy]

Updated description, tried with a small patch to test (patch for spreed Jitsi*.js files):

With webpack rule	Without rule
talk_desktop__dist\assets\JitsiEncryptionWorker.worker.js	talk_desktop__dist\chunks\spreed_src_utils_e2ee_JitsiEncryptionWorker_worker_js.js

Tried to check, how file path is resolved, but it didn't work with method tried; so check file system directly for .webpack folder

[alexbarnsley]

I can confirm that this works. I was experiencing the previous issues but built from source using this PR and calls are now working as expected