Repository navigation
baseUrl is used to create reference type path in declaration file #39695
Copy link
Copy link
Closed
Labels
BugA bug in TypeScriptA bug in TypeScriptDuplicateAn existing issue was already createdAn existing issue was already createdRescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone
Milestone
Description
Activity
sheetalkamat commented
on Jul 24, 2020 MemberAuthorMore actionsNote that this is not regression since previous release. #32878 introduced this which is around for sometime now.
sheetalkamat commented
on Aug 10, 2020 MemberAuthorMore actionsThis 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
///reference pathgets converted to an invalid///reference types.- addedRescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone
on Dec 11, 2020 6 remaining items
sheetalkamat commented
on Nov 16, 2023 MemberAuthorMore actionsDuplicate of #34749
- marked this as a duplicate of Cannot find type definition file for ambient declaration module #34749
on Nov 16, 2023 - addedDuplicateAn existing issue was already createdAn existing issue was already created
on Nov 16, 2023 - locked as resolved and limited conversation to collaborators
on Oct 21, 2025
Metadata
Metadata
Assignees
Labels
BugA bug in TypeScriptA bug in TypeScriptDuplicateAn existing issue was already createdAn existing issue was already createdRescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone
npm run buildis definitely bug and #39645 fixes that.npm run build-baseUrlwell that raises questions. #32878 started preferringtypesoverreference pathsto 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 Sheetal Nandi (@sheetalkamat) in #37928 (comment)