Language Service: does not work with "paths" from .tsconfig

[karptonite]

I'm submitting a ... (check one with "x")

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior
Set "paths" and "baseUrl" in tsconfig. for example:

"compilerOptions": {
  "baseUrl": "src",
  "paths": {
    "@myapp/*": [
        "app/*"
      ]
    },
}

Then import a component in a module using the path set via paths.

import {HeaderComponent} from  "@myapp/header/header.component";

Add {{foo}} to header.component.html. The error reported is "Unresolved variable or type foo".
The import seems to work fine, otherwise.

Expected behavior
The error should be: "Angular: Identifier 'foo' is not defined. The component declaration, template variable declarations, and element references do not contain such a member". This is the error that is reported if the import is done via a relative link, e.g, "./header/header.component"

Minimal reproduction of the problem with instructions
As described above.

What is the motivation / use case for changing the behavior?
To get proper errors via language service when using absolute paths for imports.

Please tell us about your environment:
PhpStorm 2017.1.3, MacOS 10.12.4.

• Angular version: 4.1.0

• Browser: N/A

• Language: Typescript

• Node (for AoT issues): node --version = 7.9.0

[karptonite]

Hold off on this--I'm not able to reproduce it at the moment. It may have been user error. I'm also unable to get the language service working at all, but that may be a PHPStorm issue.

[karptonite]

OK, I can now confirm that I can reproduce this bug.

I was temporarily unable to Language Service working at all due to this bug in Typescript, microsoft/TypeScript#15433, but that is now fixed, and I'm still seeing the behavior described in my initial report.

[outruller]

Is there any further info about this issue?

[jusefb]

I have the same problem would appreciate a fix for this

[karptonite]

Just to confirm This is still an issue in Angular 4.2.0.

[karptonite]

Here is a repo that anyone can pull down to reproduce the error:
karptonite/angular-test-language-service@478748d

In this case, the issue is in app.component.ts. When I import TestService with a path base on the paths param in tsconfig, as shown, I get the error message shown in the comments. If I replace the import with the relative path (commented out), no error.

This is with PHPStorm EAP 2017.2, although I hope that wouldn't make a difference.

[karptonite]

In case this is a PHPStorm issue, I've also reported this here:
https://youtrack.jetbrains.com/issue/WI-36836

[aitboudad]

not sure if it's related to PHPStorm as I've got the same issue using vscode

[aitboudad]

angular/vscode-ng-language-service#99

[ylibrach]

Can confirm that this is an issue using VSCode as well. Using a baseUrl property in tsconfig (along with paths, although I think the root issue is the baseUrl), and I cannot resolve anything imported from locations defined by the baseUrl+paths.

[ClementVidal]

I also have this issue with:

Angular version: 4.3.2
 
- Node version: 6.11.0
- Platform:  Linux

- VsCodde 1.14.2
- Angular language service plugin 0.1.4
- Angular language service 4.1.0-beta

[meriturva]

Still present on angular 4.3.6. On vscode 1.15.1 i have few errors related to: Error encountered resolving symbol values statically of symbols declared through paths property on tsconfig.json file . Any eta here? Thanks.