Hi @duncan
, I saw that you are using a separate material module for the imports. But it might become a performance issue in large applications.
The material module is given as individual components because webpack can tree-shake the rest of the unused modules. If we start using material module, webpack can't figure out if a module is used in the application or not.
I was looking for docs for the MatIconRegistry, thanks for the post.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi @duncan , I saw that you are using a separate material module for the imports. But it might become a performance issue in large applications.
The material module is given as individual components because webpack can tree-shake the rest of the unused modules. If we start using material module, webpack can't figure out if a module is used in the application or not.
I was looking for docs for the MatIconRegistry, thanks for the post.