-
Notifications
You must be signed in to change notification settings - Fork 113
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
[Docs] Tree-shaking benchmark of RN app #581
Comments
cc @matthargett |
This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days. |
This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days. |
I'd still really like to see this, especially to track new rspack versus old webpack backend as time goes on. |
This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days. |
another optimization scenario that affects React hot path: https://gitlab.com/seaofvoices/darklua/-/issues/44 |
This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days. |
This issue has been automatically closed because it has been inactive for more than 14 days. Please reopen if you want to add more context. |
Tree shaking doesn't work in module federation, is there any solution? |
Summary
Add page to docs that will showcase potential gains obtained through the use of tree-shaking.
We could also add few tips how to optimize the codebase to squeeze even more out of tree-shaking, also backed with data.
The text was updated successfully, but these errors were encountered: