Architecture constraints and TypeScript project references

SonarQube Cloud
1

I tried to activate the new architecture constraints. The project is analyzed in SonarQube Cloud, Team plan, with unmodified SonarWay profile.

We use a repository with many TypeScript projects, referring each other through TypeScript project references. In the code we import using Node module names. We do not import other projects as files.

Example:

import { Interface } from '@myProject/baseModule';

and in tsconfig.json:

...
  "references": [
    {
      "path": "../base/module"
    },
...

I wasn’t able to create an error with SonarQube configuration like this, which is wrong on purpose to provoke an error:

{
    "constraints": [
        {
            "to": ["base/**/*.ts"],
            "from": ["app/**/*.ts"],
            "relation": "deny"
        }
    ]
}

Is this scenario not yet supported?