-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parse does not work with ${configDir} variable of tsconfig.json in node_modules #188
Comments
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 |
I think I narrowed down the bug. It seems that 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:
The text was updated successfully, but these errors were encountered: