I am getting the error that "Component [name]Component must have a template or templateUrl" on all of my components. I am guessing this is because rather than using templateUrls or inline templates, I am using webpack and require() to import the templates. It would be great if the extension could resolve routes/modules that use require().
+1
Facing this as well. Can't use this at all as long as require for templates are not recognized.
So I've been investigating a bit. It seems that this can't be fixed from this package as this uses the angular language-service package to obtain the template references.
In particular, this line is interesting. Seems like the service only has knowledge of "templateUrl". If this is to be fixed, the language-service package is where this should happen. Not sure if this is feasible though.
Opened an issue in the angular repo, linked above.
Closed in angular as well.
Related Angular issue: https://github.com/angular/angular/issues/23553
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
Opened an issue in the angular repo, linked above.