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
This is what happens when I run ng build --prod. Which worked just fine with Covalent 1.0.0-rc.1, but once I upgrade to Covalent 1.0.0-rc.3 it stops working.
What is the expected behavior?
Successful build when using CovalentFileModule
What is the motivation / use case for changing the behavior?
Successful build when using CovalentFileModule
Which version of Angular and Material, and which browser and OS does this issue affect?
Angular 5.2.1
Material 5.1.0
Win 10
Chrome 63
Did this work in previous versions of Angular / Material?
It worked with older version of Covalent (1.0.0-rc.1).
Doesn't work with and version of Angular/Material with Covalent 1.0.0-rc.3
Other information
I tried both importing CovalentFileModule from @covalent/core and @covalent/core/file. Same result.
I suppose someone just removed/forgot to put @ngModule by mistake.
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Bug
Bug Report
Screenshots or link to CodePen/Plunker/JSfiddle
This is what happens when I run
ng build --prod
. Which worked just fine withCovalent 1.0.0-rc.1
, but once I upgrade toCovalent 1.0.0-rc.3
it stops working.What is the expected behavior?
Successful build when using CovalentFileModule
What is the motivation / use case for changing the behavior?
Successful build when using CovalentFileModule
Which version of Angular and Material, and which browser and OS does this issue affect?
Angular 5.2.1
Material 5.1.0
Win 10
Chrome 63
Did this work in previous versions of Angular / Material?
It worked with older version of Covalent (1.0.0-rc.1).
Doesn't work with and version of Angular/Material with Covalent 1.0.0-rc.3
Other information
I tried both importing CovalentFileModule from
@covalent/core
and@covalent/core/file
. Same result.I suppose someone just removed/forgot to put
@ngModule
by mistake.The text was updated successfully, but these errors were encountered: