Using TypeScript path aliases raises Code Smell in Sonar Qube

[WebStew]

Hi,

In my TypeScript project I am using path aliases to my files as per the below from my tsconfig.json

{ ... "paths" : { "@features/*" : "project/features/*" } ... }

SonarQube is reporting the following Code Smell for each time I call an import using the alias

Module @features/ is not listed as dependency in package.json.

Is this the correct behaviour? I wouldn't expect a Code Smell here but rather for SonarQubeTS to be aware of my path aliases?

Many thanks
Stu

[WebStew]

Closing issue as logged SonarSource/SonarTS#677 here