-
Notifications
You must be signed in to change notification settings - Fork 27.1k
using NoopAnimationsModule should produce a small bundle size #20002
Copy link
Copy link
Closed
Labels
P4A relatively minor issue that is not relevant to core functionsA relatively minor issue that is not relevant to core functionsarea: animationslegacy animations package only. Otherwise use area: core.legacy animations package only. Otherwise use area: core.area: packagingIssues related to Angular's creation of npm packagesIssues related to Angular's creation of npm packagesarea: performanceIssues related to performanceIssues related to performancefreq2: mediumstate: confirmed
Milestone
Description
I'm submitting a...
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
Current behavior
The @angular/animations size is quite large 100kb minified (62kb for animations + 40kb polyfill) even when disabling it by using NoopAnimationsModule (60kb).
Before 4.3 it was about 30kb.
Expected behavior
at least I would like to have a small size when using NoopAnimationsModule.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P4A relatively minor issue that is not relevant to core functionsA relatively minor issue that is not relevant to core functionsarea: animationslegacy animations package only. Otherwise use area: core.legacy animations package only. Otherwise use area: core.area: packagingIssues related to Angular's creation of npm packagesIssues related to Angular's creation of npm packagesarea: performanceIssues related to performanceIssues related to performancefreq2: mediumstate: confirmed