You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been testing aragon OS framework and made our custom app. There were many problems with that alone. We noticed that when publishing the app, the GUI folder is huge (at first it was ~50MB, the second build was ~36MB). IPFS sucks for huge folders because the gateway has to clone the whole repo and takes hours for the aragon ipfs gateway to sync this custom app GUI folder. When it is finally available, the aragon client loads only 12MB from this huge dist folder.
I saw there are lots of javascript and css maps as well as all of the aragon-ui source code (~11MB).
Is there a way to export an optimized GUI that is not 3x the size of the actual app? Do we really need to do "copy-aragon-ui-assets" before building? Shouldn't there be a centralized aragon-ui (and also for other dependencies) public production repo that apps can use? The actual apps GUIs are really really small. Just a bunch of buttons and layouts. We really don't need to have a full copy and a compiled copy of aragon-ui and all of the other dependencies.
The text was updated successfully, but these errors were encountered:
We have been testing aragon OS framework and made our custom app. There were many problems with that alone. We noticed that when publishing the app, the GUI folder is huge (at first it was ~50MB, the second build was ~36MB). IPFS sucks for huge folders because the gateway has to clone the whole repo and takes hours for the aragon ipfs gateway to sync this custom app GUI folder. When it is finally available, the aragon client loads only 12MB from this huge dist folder.
I saw there are lots of javascript and css maps as well as all of the aragon-ui source code (~11MB).
Is there a way to export an optimized GUI that is not 3x the size of the actual app? Do we really need to do "copy-aragon-ui-assets" before building? Shouldn't there be a centralized aragon-ui (and also for other dependencies) public production repo that apps can use? The actual apps GUIs are really really small. Just a bunch of buttons and layouts. We really don't need to have a full copy and a compiled copy of aragon-ui and all of the other dependencies.
The text was updated successfully, but these errors were encountered: