Issue: Dependency cruiser is unable to correctly resolve aliases defined using "paths" in tsconfig that start with '/' (tsconfig-paths issue)

We are currently using ViteJS as our devServer, and the condition to define alias there is that it should start with a forward slash (/). If you want to know why is that the case, checkout this link.
Thus our paths property in tsconfig.json looks like this

"paths": {
  "/@utils/*": ["src/utils/*"]
  "/@services/*": ["src/services/*"],
  "/@contexts/*": ["src/contexts/*"],
  "/@src/*": ["src/*"]
},

Earlier when we were using the aliases without / dependency cruiser was working perfectly fine, eg: defining alias like "@utils/*": ["src/utils/*"], works.

Expected Behavior

Dependency cruiser should be able to resolve the aliases correctly

Current Behavior

It is not able to resolve the aliases correctly. As can be seen from the example shared below to reproduce the issue, it’s treating the alias as a separate directory. link

Possible Solution

Not sure.

Steps to Reproduce (for bugs)

Following repo can be used to reproduce the issue https://github.com/surgicaI/dependency-cruiser-repro

Context

We want to use dependency cruiser to add forbidden dependency tests and due to this bug we are not able to do so.

Your Environment

• Version used:9.8.0
• Node version:14.7.0
• Operating System and version:MacOS Catalina
• Link to your project:N/A