0

I've a HUGE problem. The entire thing started with this: Fix corrupted HTML file or decompile Angular Component

My PC suddently crashed and from that event it become worse every second. I get weird errors such as "'app-component' is not a known element" or "No pipe found with name 'async'" or even "Can't bind to 'attribute' since it isn't a known property of 'app-component". I get this for many components.

What I did:
I immediately deleted the corrupted file I talked in this other thread and I started to look at EVERY piece of code. EVERY error. But it seems all fine for me. It's fine even for Visual Studio Code, because it didn't trigger any error/problem to me as you can see here: VSC Terminal Screenshot

I really don't know what should I do.

Here you can find the repository:
https://github.com/plungarini/alpha-project

7
  • Nobody here will clone your repository, that's beyond the scope of this site. However, if you have it all in a repository, have your tried deleting everything locally and tried cloning it again? If that doesn't help, have you tried going back commit by commit? Commented May 26, 2021 at 14:32
  • what heppend if you save corresponding ts file and module.ts file twice. same problem that i am facing right now, but after saving above files it runs perfectly Commented May 26, 2021 at 15:05
  • @RaviGajera I don't understand. What have you done? Commented May 26, 2021 at 16:05
  • See, I am not getting error at run time but whenever I edit my code sometimes it gives can't by ngIf , example-app is not a a know element and then I save( ctrl + s ) my corresponding ts file and module.ts file and the errors are gone. It worked because I have properly imported everything and not have any syntax error . Same problem is occurred every day in my life in angular 10. But just save again Commented May 26, 2021 at 16:54
  • @RaviGajera I tried saving again, but it's not working for me. I even tried to start again the build, but nothing... it doesn't work Commented May 26, 2021 at 17:12

1 Answer 1

0

I fixed the whole thing. There was an error in the dashboard-routing.module.ts

I wasn't loading another module required to be correctly functional. I was loading instead a component.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.