-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
baseUrl is used to create reference type path in declaration file #39695
Comments
Note that this is not regression since previous release. #32878 introduced this which is around for sometime now. |
This needs more work and time to bake in so we can emit correct paths and falls into type reference resolution and declaration emit to match those expectations and hence kind of dependent on #39708 |
This seems related to #34749 ? Presence of the baseUrl is breaking compiles in my project because |
Duplicate of #34749 |
npm run build
is definitely bug and #39645 fixes that.npm run build-baseUrl
well that raises questions. #32878 started preferringtypes
overreference paths
to make it more portable. But our resolve type reference name doesnt use baseUrl so this is kind of questionable.Other way to look at it would be when file is referenced throught only referece path from root file tree (or relative imports) prefer relative path instead of portable path.
Originally posted by @sheetalkamat in #37928 (comment)
The text was updated successfully, but these errors were encountered: