App size

[sangyoo91]

My basic app is already over 200MB.

Is it normal that apps built with electrify take this much disk space?

[arboleya]

• Yes, an empty Electron app, alone, have around 100MB. Which sounds like a lot for me, I don't know if there's a way of cutting this size down. Do you know something?
• As for the Electrify role in this, well it includes the binaries for NodeJS & MongoDB for running the Meteor app locally, so you can expect some extra 50mb ~ 70mb (depends on the platform).
• All the rest is pure code, resolved dependencies, assets and database.

My compiled todo-list app have around 30MB of code/dependencies and 60MB for the binaries -- 198MB in total.

The approach discussed in #24 would possibly remove around 100MB from the final build, since there will be no binaries or endless dependencies.

[ghost]

Hi!

I'd like to bump this question up: since upgrade to meteor 1.3 (that uses a lot of npm modules now) my packaged app has grown to almost 400 mb (comparing to 200 on meteor 1.2). File count is up to 27,000 (twenty sevent bloody thousands) comparing to ~7000 on meteor 1.2, some of them exceed windows file path limit.
Well, it's kind a frustrating now to wait for 20 minutes (twenty!) to package app.
How can I reduce file count?
Possible solutions:

• package parts of my app (at least node_modules I think) to asar archives
• delete debugging information (*.map, css-parts, sass, etc)
• delete npm_modules build information (I believe some node packages come disassebled and being compiled in meteor build stage)
• prebuild electron part of app and replace only meteor part of application during build

PS: from electron-packager readme:

Be careful not to include node_modules you don't want into your final app. electron-packager, electron-prebuilt and .git will be ignored by default. You can use --ignore to ignore files and folders via a regular expression. For example, --ignore=node_modules/package-to-ignore or --ignore="node_modules/(some-package[0-9]*|dev-dependency)".