-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
ERROR :in Ng2DeviceDetector is not an NgModule #4
Comments
I am also getting ERROR in Ng2DeviceDetector is not an NgModule error after upgrade Angular Cli (@angular/cli: 1.0.0-rc.1). It was working fine with with angular-cli:1.0.0-beta.28.3 |
@karan83 , @Faris-AH . The issue is with the recent angular-cli versions which is opened here The issue is that when you serve the first time, it throws this error. The quick workaround (until angular-cli resolves this issue) is :
The error should have gone by now. |
Hacks always work.Thanks. |
@AhsanAyaz , Thanks for reply. I did development same way you mentioned. It does show error only first time, but my concern is that i am not able to make build for production. |
@karan83 . Since this is an issue with angular-cli, i'm not sure if there's a way to make the build successful except downgrading to |
Thanks for the module. This is still an issue with angular 4 and the latest cli (1.0.1). I'm not able to get it to compile with it commented out. Are you sure it is a bug with angular-cli? |
I just took all the code from the node_modules package and made my own module, and service inside my app. So I can produce builds now. |
Any chance that you could share that module, to save me having to do the exact same thing? |
device.module.ts
device.service.ts
device-constants.ts
retree.ts
|
This problem will fixed when we upgrade to the verison ng2-device-detector@1.0.0.
in app.module -> |
cloned a fresh project using angular cli .
shows "ERROR in Ng2DeviceDetector is not an NgModule"
The text was updated successfully, but these errors were encountered: