fix: Remove MaterialModule #6803
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: MaterialModule will no longer be available.
MaterialModule
has been deprecated since beta.3 and is now being removed.From beta.3 changelog:
MaterialModule
MaterialModule
(andMaterialRootModule
) have been marked as deprecated.We've found that, with the current state of tree-shaking in the world,
that using an aggregate NgModule like
MaterialModule
leads to toolsnot being able to eliminate code for components that aren't used.
In order to ensure that users end up with the smallest code size
possible, we're deprecating MaterialModule, to be removed in the a
subsequent release.
To replace
MaterialModule
, users can create their own "Material"module within their application (e.g.,
GmailMaterialModule
) thatimports only the set of components actually used in the application.