Request: use typescript language server to trace imports

[james-yeoman]

Rather than trying to process imports by hand (which is causing problems with Typescript Path Aliases and baseUrl), why not resolve imports with the help of the Typescript Language Server?

This would allow you to reuse information that the Language Server has already covered edge cases for.

It would also be more maintainable, since your extension would only need to worry about traversing the import tree to find react components and their properties

[nicofishman]

+1 here, not working with path aliases