no-missing-import does not work with "paths" from "tsconfig.json"

[Zamiell]

In a monorepo, you typically use the "paths" option inside of the "tsconfig.json" file to make your individual packages aware of each other like this:

tsconfig.json

{
    "paths": {
      "foo": ["packages/foo/src/index.ts"],
      "bar": ["packages/bar/src/index.ts"],
    },
}

However, this triggers false positives for no-missing-import.

[wdzeng]

Any updates on this?

[scagood]

🤔 I have not had this issue in my monorepos, could you make a small reproduction repository?

---

Here are a couple of screenshots from a yarn v3 repo:

---

I have not needed the "paths" property at all for importing files, I have only needed this for importing additional types that I don't directly import, eg in another package:

---

For reference, I do think we should add paths support into the plugin. I just also want to understand why the current method of checking imports does not work 👀

[scagood]

I think I found the issue, it turns out that when the depended upon package is not built (at least once) then the file shows up as missing!