-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ngCompiler.ReflectorHost is not a constructor #3668
Comments
Same. Perhaps it would be good to report the version of TypeScript as well. I've a feeling I'm going to get asked what it is
|
ok, so I was told to try following the upgrade options specified in README.md... afterwards it now works.
How can everything work now with the exact same versions as above? I'm starting to think that angular-cli should ship with a yarn.lock to ensure dependencies are exactly the same regardless of cache on every machine |
You're totally right for Typescript. I'm using Having a yarn.lock would be good but in case of conflicts with users when upgrading, might be more complicated, what do you think ? |
Same issue with beta.24
NOTE Update: Setting local version of cli back to beta.22-1 (global still 24) resolves the above error and products another one/hangs on the following lines at 21%:
|
It stops on 21% for me as well. I have the exact same setting as you. So, for now I'm downgrading back to angular 2.2.3 (router 3.2.3) and angular-cli beta.22-1 |
@dojchek we're talking about beta-24 here and look what I wrote in the topic :
So with beta-24, we just can't downgrade to 2.2.3 |
@maxime1992 |
This is basically an issue with Angular 2.3+ and |
+1 |
Seems to be fixed in latest now. See #3426 (comment) regarding TS2.1 compatibility. |
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?
Ubuntu 16.10
Versions.
(I did also try with 2.2.4 but I get
This version of CLI is only compatible with angular version 2.3.1 or better
and with 2.4.0 but it's not working either).Repro steps.
Upgrade an app to beta-24
ng serve
The log given by the failure.
Mention any other details that might be useful.
As #3607, #3587 are now closed, I decided to open a new issue because it was supposed to be fixed in beta-24.
(at least, I presume you were talking about beta-24 @hansl)
The text was updated successfully, but these errors were encountered: