-
Notifications
You must be signed in to change notification settings - Fork 12k
Error: ngCompiler.ReflectorHost is not a constructor #3241
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
I think this is due to the angular 2.2.2 moving ReflectorHost to As a temporary workaround, I've locked my versions to 2.2.1 for |
I think you are correct. Because with version 2.2.1 everything is working fine :( |
Previously, this was part of the `AotCompilerHost`. The `AotCompilerHost` is now also greatly simplified.
Thanks. But i dont use angular-cli. I have backed all angular2 deps to 2.2.1 version until it be solved. |
Workaround for this known issue: angular/angular-cli#3241
@PRSolucoes Yes, we also updated the peer dependency of the webpack plugin. This will be resolved properly in the future (next week, because this week is thanksgiving). In the meantime you have to use Angular v2.2.1. This is unfortunate and we're looking at long term solutions to prevent this in the future. |
I'm not sure why HanZ closed this. Everything was working perfect for me with angular-cli-b21, this morning i update angular-cli-b22, tried to build, and i was looking at the error in my console. Same error mentioned above. I'm certain this has something to do with minor project configuration impedance, and you might like to call it a bug, no bug has ever stopped me before, so why would this one stop me now? And, no, I'm not rolling back any of dependencies, i keep everything on the bleeding edge. |
I'm also seeing this issue with |
Same here with angular 2.3.0. Please re-open. |
Also same problem. Angular: 2.3.0 |
Same with my project too! Angular: 2.3.0 |
@hansl any news on this |
For those subscribed to this issue, there's a bit more detail on another issue: #3467 (comment) |
Angular: 2.3.0 (also tried with 2.2.3) Same here, I don't think as correct @colemickens said in the other issue that is productive to close the issues when they are still actually issues, because people cannot track internal "tickets" of the team @hansl. Please re-open or update the subscribers for the process. |
Same issue here.. Using angular-cli": "1.0.0-beta.22-1 and angular 2.3.0 |
Same here with |
I ran into this problem after updating angular-cli from |
@kevinsherman what version of angular are you using? |
|
Seeing the same problem as above with both 2.2.4 and 2.2.3. |
I was able to get the angular 2.3.0 working downgrading the angular-cli from version [email protected] to version [email protected]. Now the error has gone. |
@reginaldocmrg WOW that worked! |
How do you actually rollback, though? I performed a global install of [email protected], after global removing 22, and still have .beta22! I feel liked I'm negotiating with a cartoon. |
I installed [email protected] locally. |
@Adrriver it worked well for me sudo npm uninstall -g angular-cli
sudo npm install -g [email protected] |
@Adrriver solution works for me also... |
I'm getting the same error but I'm not using angular-cli. I'm using webpack. My package.json looks like this |
@mahindar5 Error actually comes from webpack, either you use ng cli or not. |
Hi @stanislavromanov is there any workaround to fix this? Thanks |
Tried all suggested solutions still nothing working. |
@daviddsingleton you need angular 2.2.4 (and 3.2.4 for router) |
Same issue here with 1.0.0-beta.23, as in (#3501, #3467 and #3367). Besides the problem building, I do not know why UNMET PEER DEPENDENCY message when installing latest CLI release.
|
Has progress?i has same issuse,i used webpack(2.1.0-beta.25) @angular(2.2.3) @ngtools/webpack(1.1.9) |
had the same problem with beta 24, try creating a new project , then copy your source folder to that new project. then modify config files as required. It worked for me. |
I had the same issue; all that was required to fix it was to remove If you're using yarn you need to remove both |
@mgol Thanks a lot, the problem was with yarn. I removed the yarn.lock and it's now working ! |
getting same error with angular 2.4.1 . Any specific details on which version of angular AOT works ? |
@arunswaminathank Have you tried removing node_modules (and yarn.lock if you use yarn) and reinstalling dependencies? |
Yes, I tried , still the same error
…On 04-Jan-2017 5:04 PM, "Michał Gołębiowski" ***@***.***> wrote:
@arunswaminathank <https://github.com/arunswaminathank> Have you tried
removing node_modules (and yarn.lock if you use yarn) and reinstalling
dependencies?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3241 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATftz-WUvXjQHyMBgMi-cPNyvpWl3NUtks5rO4OqgaJpZM4K6EUT>
.
|
This is unreal. I can't build my project about 2 weeks. Every combination of versions gives different errors. |
I'm using AOT with
|
Let me try that today too. I put my prj on hold because of these issues like 3 weeks ago. Let's hope it'll work... |
Still does not work. This is ridiculous. |
Was there a fix for this? I am experience this as well :( |
That's fixed pretty long time ago. My suggestion is to create a new project with beta.26 (the current version as I write this). |
I update all package to last version,the issuse fixed. |
I use this package.json and fixed! |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Versions.
Repro steps.
The log given by the failure.
Mention any other details that might be useful.
My plugin initialization:
The text was updated successfully, but these errors were encountered: