-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
TypeError: Cannot read property 'flags' of undefined #35021
Comments
I think it's work well. what version of |
I was able to reproduce the same issue trivially by following the exact steps given using
Presumably the issue depends on Typescript's js support. |
No, it's more likely that the binder doesn't recognise this construction as a class and doesn't mark it with the It's probably related to syntactically locating |
I'm using angular 5 and ionic v3. For me work these changes: Be sure that not use Be sure to remove your node_modules and do |
Hi,
current updated to latest which is
Can somebody help me please. |
Same here. Package Version@angular-devkit/architect 0.901.4 Thanks for your advise! |
Same here, I am having this error too. after updating from angular 9.1.4 to 9.1.5
how to fix this issue? |
Can you compare the package.json? |
I'm having same issues on 9.1.4 |
Same here. Created a new app just a few hours ago and got the same error set as others before in this thread.
Angular: 9.1.5 Package Version@angular-devkit/architect 0.901.4 |
Please help...! Any solution for the latest update????????? |
BTW, this is a closed issue. |
I have the same problem, It worked yesterday。
somebody can help me? |
solution :
|
Something is broken in Angular 9.1.5 - if you run the following it should work: npm install @angular/core@9.1.4 @angular/animations@9.1.4 @angular/common@9.1.4 @angular/forms@9.1.4 @angular/platform-browser@9.1.4 @angular/router@9.1.4 @angular/platform-browser-dynamic@9.1.4 @angular/compiler@9.1.4 @angular/compiler-cli@9.1.4 @angular/language-service@9.1.4 ng build The issue seems to stem from using Angular CLI 9.1.4 with Angular 9.1.5 (most likely the compiler You'll see the issue when you do ng --version Angular CLI: 9.1.4 Angular: 9.1.5 |
Do delete node_modules and delete package-lock.json and run
and do ng serve. it worked for me. check this stack overflow (https://stackoverflow.com/questions/61670882/error-in-typeerror-cannot-read-property-flags-of-undefined/61671596#61671596) |
this worked for me. Thanks |
it's worked. thanks |
in addition, I had to execute a separate |
This works for me. Thanks. |
This worked for me. |
this is only downgrade, not fix |
Hi @nikitanewmsk Thank you so much for immediate reply. But it is I'd done waiting for fix now. :) |
Hello everyone , My problem is solved by downgrade which is probably not a fix at all but it works ! @shikhasreekumar99 : thank you 👍 Step 1 : 👍
Step 2 : 👍RUN THIS COMMAND ON YOUR CONSOLE Step 3 : 💯CONGRATULATIONS YOU SUCCESSFULLY DOWNGRADED THE DEPENDENCIES AND THE TYPEERROR IS RESOLVED SUCCESSFULLY SCREEN SHOT OF SUCCESFULL NG SERVE |
its worked for me! |
I'm getting same error while tsc tries to compile highcharts.js using tsc 3.8.3 with node 10. Interestingly babel doesn't fail, but tsc does. Well the error doesn't tell me which line is faulty, so I'm going down the rabbit hole to debug this out in tsc. Will get back with offending line. Okay debugging through tsc at 1am in the morning isn't being very helpful. The node positions point me to this area
Is there a way to tell tsc not to parse jsdoc types in comments in js files when in transpile only mode. It's really surprising that transpileOnly makes tsc error out. Here's the full file if tsc team wants to investigate. I will keep on digging deeper. |
Same error angular 10. Tried downgrading to 9.1.4, no difference, nothing works "dependencies": { |
Are you using Yarn? I am getting this error when using yarn |
still an issue. "@angular/animations": "^10.1.0", Edit:
|
TypeScript Version: 3.7.2
How to reproduce
test.js
tsconfig.json
tsc
Expected behavior:
no errors
Actual behavior:
Playground Link:
Related Issues:
The text was updated successfully, but these errors were encountered: