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

Compiled code became ~30% larger in v22.0.0+ #1895

Closed
tommoor opened this issue Jan 2, 2023 · 5 comments
Closed

Compiled code became ~30% larger in v22.0.0+ #1895

tommoor opened this issue Jan 2, 2023 · 5 comments

Comments

@tommoor
Copy link

tommoor commented Jan 2, 2023

🐛 Bug Report

The codebase became ~30% larger without any functional changes, it would be nice to track down what caused the increase and knock this bundle back down to the smaller size.

image

To Reproduce

See bundlephobia:

@adrai
Copy link
Member

adrai commented Jan 2, 2023

Why are you saying "without any functional changes"?

between v21.0.0 and v22.0.0 there were a lot of changes...

for example v21.3.0 added support for formats provided by Intl API: https://github.com/i18next/i18next/blob/master/CHANGELOG.md#2130

and v21.5.0 added named export support and updated some babel dependencies: #1681

etc....

@adrai
Copy link
Member

adrai commented Jan 2, 2023

I don't think there's much we can do...
If you have any idea to decrease the size, let us know...

@tommoor
Copy link
Author

tommoor commented Jan 2, 2023

Yes sorry – It's hard on bundlephobia to see a graph over time of the sizes so I'm just comparing one by one. It seems that the biggest change was in this release:
https://github.com/i18next/i18next/releases/tag/v21.5.0

@adrai
Copy link
Member

adrai commented Jan 2, 2023

like said... no idea how to reduce size without removing functionality...
feel free to contribute if you have an idea...

@tommoor
Copy link
Author

tommoor commented Jan 2, 2023

I will close the issue as I was initially under the impression that the increase was sudden from a change in the build process.

Just as a side note it's kind of worrying that this dependency is so large and continues to get bigger with every update, as it does not lend itself to code splitting and needs to be in the initial bundle due to it's inclusion in every component

Many thanks.

@tommoor tommoor closed this as completed Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants