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
When building a project it seems that tree-shaking is not working as expected. The entire codebase from the package is being bundled, even though only a subset of the modules is being used in the final build.
A main suspect is the Launchexport, it is setting up all the initial configs for the different SDK modules. Also, we found setting sideEffects: false on the package JSON of the SDK reduce the bundle size a bit.
Steps to reproduce
No response
Expected Behavior
Tree-shaking should remove unused modules from the build, resulting in a smaller bundle size containing only the necessary code.
Actual Behavior
The full codebase from the package is included in the final build, which increases the bundle size unnecessarily.
Notes (Optional)
Version of the package: 5.5.4
The text was updated successfully, but these errors were encountered:
Problem/Opportunity
When building a project it seems that tree-shaking is not working as expected. The entire codebase from the package is being bundled, even though only a subset of the modules is being used in the final build.
A main suspect is the
Launch
export, it is setting up all the initial configs for the different SDK modules. Also, we found settingsideEffects: false
on the package JSON of the SDK reduce the bundle size a bit.Steps to reproduce
No response
Expected Behavior
Tree-shaking should remove unused modules from the build, resulting in a smaller bundle size containing only the necessary code.
Actual Behavior
The full codebase from the package is included in the final build, which increases the bundle size unnecessarily.
Notes (Optional)
Version of the package: 5.5.4
The text was updated successfully, but these errors were encountered: