ElectronNET/Electron.NET

Publish Output Performance

Aberta

#979 aberto em 12 de dez. de 2025

 (16 comentários) (2 reações) (0 responsável)C# (710 forks)batch import
enhancementhelp wanted

Métricas do repositório

Stars
 (7.040 estrelas)
Métricas de merge de PR
 (Mesclagem média 4d 13h) (7 fundiu PRs em 30d)

Description

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 <dir>), 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 (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?

Guia do colaborador