Closed throrin19 closed 8 months ago
Hi @throrin19 thanks for raising this issue. It worried me a bit so I've attempted to create a minimal reprodution sample - see dependency-cruiser-repro-repo/909. The issue doesn't repeat there, however, which means there's a difference between the private repo and that one.
"type": "module"
"@version": ["./src/version.ts"]
)'@version'
--init
and stripped from all comments and rules not relevant for the issue.I found the problem. I made alias to .js
file, no to the real .ts
file and it works fine after change that.
Sorry for this mistake and thanks for your help :)
Expected Behavior
Hello, I migrate all my project from CJS/ESM mix to pure ESM (very messy js ecosystem). Normally all my defined rules before migration should work correctly.
Current Behavior
After that I have several errors for specific imports using TS aliases. For all this aliases, I don't use extension, it's a one:one link (I think the problem is here)
Possible Solution
I don't know, specific settings to set for this aliases, no extension is needed and read correctly alias target
Steps to Reproduce (for bugs)
In my case, I have this tsConfig:
All works fine for compilation part. But I have all this errors after depcheck :
Your Environment