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
This is just in it's very very early stages and was inspired by this tweet: while we have decided some time ago that we do not completely optimize for bundle sizes on releases (and e.g. also include the source along with the distribution): when looking of what our bundle sizes compose of e.g. with bundlephobia for the VM one is seeing that this has some serious tilt with just three - somewhat - side libraries very much dominating the whole package:
Again, very early stages and we shouldn't draw overly hastily any conclusions from this.
But we might want to at least have a look and take this into consideration among other aspects for the next round of breaking releases.
As a side note: so for Common e.g. this mainly comes (I'm quite sure) from the large mainnet genesis state we are shipping with it. Not sure if we want or can do something about this and if there are structural alternatives here.
The text was updated successfully, but these errors were encountered:
Actually: will reopen and just take the above comment as an update. While the bundle size reduction in Common is a big step we might want to have a continued look here e.g. regarding the VM bundle size also influenced strongly by other packages as can be seen in the diagram above.
This is just in it's very very early stages and was inspired by this tweet: while we have decided some time ago that we do not completely optimize for bundle sizes on releases (and e.g. also include the source along with the distribution): when looking of what our bundle sizes compose of e.g. with bundlephobia for the VM one is seeing that this has some serious tilt with just three - somewhat - side libraries very much dominating the whole package:
Again, very early stages and we shouldn't draw overly hastily any conclusions from this.
But we might want to at least have a look and take this into consideration among other aspects for the next round of breaking releases.
As a side note: so for Common e.g. this mainly comes (I'm quite sure) from the large mainnet genesis state we are shipping with it. Not sure if we want or can do something about this and if there are structural alternatives here.
The text was updated successfully, but these errors were encountered: