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

Convert @angular/material imports to make them tree shakable #44

Closed
thienedits opened this issue Aug 27, 2018 · 2 comments
Closed

Convert @angular/material imports to make them tree shakable #44

thienedits opened this issue Aug 27, 2018 · 2 comments
Assignees

Comments

@thienedits
Copy link

Please look at the material2 issue and specifically the comment from the link below:

angular/components#4137 (comment)

kuhnroyal pushed a commit that referenced this issue Dec 14, 2018
Signed-off-by: Peter Leibiger <kuhnroyal@gmail.com>
kuhnroyal pushed a commit that referenced this issue Dec 14, 2018
Signed-off-by: Peter Leibiger <kuhnroyal@gmail.com>
kuhnroyal pushed a commit that referenced this issue Dec 14, 2018
* ban '@angular/material' import

Signed-off-by: Peter Leibiger <kuhnroyal@gmail.com>
@kuhnroyal kuhnroyal self-assigned this Dec 14, 2018
@kuhnroyal
Copy link
Owner

I am not seeing any difference in the bundle size of the sample app. Tree-shaking works either way but I guess it doesn't hurt.
bundle_after

kuhnroyal pushed a commit that referenced this issue Dec 16, 2018
* ban '@angular/material' import

Signed-off-by: Peter Leibiger <kuhnroyal@gmail.com>
@bbortt
Copy link
Collaborator

bbortt commented Oct 30, 2019

This is a "must have" withing angular/v8+, I think. was partially done in #73 . will take a look at and merge #57 anyways.

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

3 participants