-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
v4 fails on resolving common libraries outside root #87
Comments
Use |
Thanks! for quick response. 3.6.0 also has same logs but bundling works, in case of 4.0.3 bundling fails. o/p of
|
Seems like |
@aleclarson it is used for sure, else I am getting error
Debug is not working for both commands I'll send you a test repo, if that helps |
That would help |
get same issue:
|
@Ludea That seems to be a different issue (not a similar error message). |
Should I open a new issue to track this ? |
The folder doesn't exists into node_modules |
Then it's not an issue with this plugin or |
@aleclarson sorry for the delay. please find the rep : https://github.com/janakg/tsconfig-path-lib-path-issue Just switch between version 3.6.0 and 4.0.3 of vite-tsconfig-paths , currently it works only in 3.6.0. Also, i don't know how to get the debug log working in this setup As I have mentioned before this is via electron-vite (it is a thin wrapper library on vite for ease of use for electron apps) |
Thanks for the reproduction. No estimates on when I'll be able to take a look though. Hopefully someone else will step in and investigate! |
sure, thanks for the update. we will stick to 3.6.0 for now. |
I believe that this bug is introduced by this commit: Since this commit, this plugin doesn't resolve any import path when the importer is not a descanter of the tsconfig file specified by How can we fix this? I can contribute a PR about this. |
v3.6.0 works for a module outside the root, but v4 fails.
example:
tsconfig::
The text was updated successfully, but these errors were encountered: