Electrifying my meteor app on MacOS, with every call of:
electrify package -- --icon /path/to/icon.icns
our Project.app grows about 400 MB (without me ever running the app, just consecutive package runs!). After 1st call the app is 240MB, then 680MB, then 1.1 GB, then 1,5 GB.
If I kill the ".dis" directory, the app is initially build with 240 MB, again.
Whenn digging into the created app package (bundle), I see that inside the huge outer app, multiple recursive .dist directories are stored in there... So, not only exists .electrify/.dist/Project.app - but also inside there lives a further ".dist" here:
- .electrify/.dist/Project-darwin-x64/Project.app/Contents/Resources/app/.dist and in there:
- .electrify/.dist/Project-darwin-x64/Project.app/Contents/Resources/app/.dist/Project-darwin-x64/Project.app/Contents/Resources/app/.dist
... and so on.
With every call to electrify a further ".dist" is embedded into the app.
Electrifying my meteor app on MacOS, with every call of:
electrify package -- --icon /path/to/icon.icnsour Project.app grows about 400 MB (without me ever running the app, just consecutive package runs!). After 1st call the app is 240MB, then 680MB, then 1.1 GB, then 1,5 GB.
If I kill the ".dis" directory, the app is initially build with 240 MB, again.
Whenn digging into the created app package (bundle), I see that inside the huge outer app, multiple recursive
.distdirectories are stored in there... So, not only exists .electrify/.dist/Project.app - but also inside there lives a further ".dist" here:... and so on.
With every call to electrify a further ".dist" is embedded into the app.