Publish Output Performance

I have a few questions regarding the publish output which I couldn't really find an answer to so far:
- Why is the output so large? The .NET runtime should be around 80-100MB and the electron binary around 150MB. Yet my current output (from the example Blazor Web App project) is more than 500MB as compressed binary.
- I _think_ some content is also packaged twice. This can be observed either by unpacking the `app.asar` file (`npx @electron/asar extract app.asar `), or by setting `asar` to `false` in the `electron-builder.json` file. The archive content under `app.asar/bin` seems to exist twice?
- Is there any way to reduce the bundle size of the electron package? I've seen some reports that claim they managed to reduce their electron apps to [below 50MB](https://github.com/electron/electron/issues/2003) (or even less in some cases). Is the `node_modules` directory even required?

Furthermore, the startup time from launching the app via the published .exe file seems rather large? Does it extract the content _every time_ you open the app?

Comece com a saída .exe publicada e a configuração de electron-builder.json mencionada na issue. Inspecione o app.asar descompactado, especialmente app.asar/bin, e compare-o com o conteúdo de node_modules e o comportamento na inicialização. O trabalho estará concluído quando for identificado se há conteúdo duplicado, quais conteúdos dos pacotes são necessários e o que causa o grande atraso na inicialização.

Escrita pelo modelo de indexação a partir do texto da issue.