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
I believe it would be better to remove the Material Icon font from the platform.css and do it like Material 2 (include <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet"> in the html).
Trying to use Covalent with an existing webpack build system is not that nice because the font cannot be loaded properly.
The text was updated successfully, but these errors were encountered:
hmmm, one of the main reasons we built Covalent was to make using Angular-Material easier to use with everything an app needs out of the box...like not having to include the font separately...
I think your point is valid but instead we need to focus on better manual inclusion docs so you can easily cherrypick covalent modules
I believe it would be better to remove the Material Icon font from the platform.css and do it like Material 2 (include
<link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">
in the html).Trying to use Covalent with an existing webpack build system is not that nice because the font cannot be loaded properly.
The text was updated successfully, but these errors were encountered: