Closed Zamiell closed 3 weeks ago
please provide a link to a minimal reproduction, not a huge monorepo.
Sorry, I don't currently have the cycles to provide a minimal reproduction. For now, I will use parseNative
, and I guess we can leave this issue open to see if anyone else has the same problem.
I think I narrowed down the bug. It seems that tsconfck
does not parse npm packages correctly, as demonstrated by the following reprex: https://github.com/Zamiell/test
If you copy paste the remote tsconfig and put it in the repo root, then everything works fine. Thus, I guess the logic for resolving npm packages isn't working properly?
please check #189 and lmk if that works for you. I did add a testcase based on your config so it really should ;) Thanks for the reproduction
thanks, that does seem to fix the problem!
fix released in 3.1.2
steps to reproduce: