-
Notifications
You must be signed in to change notification settings - Fork 40
Unable to build when adding angular2-logger to angular-cli managed project #113
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
Comments
Same issue for our project |
Same for me, it happened with the update of angular-cli 1.0.0-beta-24 to 1.0.0-beta-25.5. It worked with beta-24. |
I tried downgrading to angular-cli 1.0.0-beta.24 and I get the same error.
|
we have the issue. please fix |
Was working fine with AngularCLI Beta .21. Upgraded to .25.5 and this error occurs. Interestingly, I see that the core team have implemented a logger in 25.5 CLI : angular/angular-cli@e3b48da |
I have the same issue (worked with beta 24) and I found a way to avoid the problem. |
Hello all, Really sorry you are all running into these issues but I won't be making any changes based of a beta product, when you use a beta software you are bound to have issues eventually and things will be changing, I can't fix it everytime they brake something. If someone has a pull request with the fix I don't mind taking a look at it. |
Fair enough - good point |
The fix by @eservent seems to work for me too - thx |
workaround by @eservent is working - but it is annoying to have to adjust all the imports all the times, because the IDE will not use that import automatically (at least intelliJ doesnt). I think it is bad that they broke that in the CLI - maybe we should file it as a bug there? |
@bruderol certainly worth a try. |
So could please someone open a bug at Angular-CLI, who has some more insight into the details of this? Thanks! |
Probably this already fixed in Angular-cli, angular/angular-cli@e91552f So might wait for next release of the cli or if you are like me then I found an alternative logger for AOT support here. @langley-agm I hope you wouldn't mind another logger linked here. Just info for others. |
@chunghha not a problem ! |
i have the same problem in @angular/cli 1.0.0-beta.30 with AOT build. |
It might help that the problem doesn't occur if I have just a single import { Logger } from 'angular2-logger/app/core/logger'; in my code. All other import statements can use @langley-agm, since the Angular-CLI is now out of beta and this problem still occurs, it might be worth looking into it. The proposed workaround doesn't do it for my anymore because with it, Furthermore, it might be helpful to look into angular/angular-cli#4072 (comment) where a seemingly similar issue is discussed. |
I have the same problem using @angular/cli 1.0.0-rc.1
|
@mastertinner workaround worked with @angular/cli 1.0.0-rc.1 & 2. |
@mastertinner This worked for me too. Many thanks. |
Closing this, for follow up you can use #79 |
If I build my angular-cli project which has the angular2-logger dependency, I get the following error:
The error can be reproduced by doing the following:
Then edit the src/app/app.module.ts and add the import:
and add the provider:
The text was updated successfully, but these errors were encountered: