Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monorepo: Analyze Bundle Sizes #1673

Closed
holgerd77 opened this issue Jan 29, 2022 · 3 comments
Closed

Monorepo: Analyze Bundle Sizes #1673

holgerd77 opened this issue Jan 29, 2022 · 3 comments

Comments

@holgerd77
Copy link
Member

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:

grafik

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.

@holgerd77
Copy link
Member Author

Bundle size will be dramatically reduced by #1916 (MB -> KB), will close here.

@holgerd77
Copy link
Member Author

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.

(mid-term task for after the releases as well 😋)

@holgerd77
Copy link
Member Author

So much bundle work lately, will close here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant