Skip to content

baseUrl is used to create reference type path in declaration file #39695

Description

npm run build is definitely bug and #39645 fixes that.

npm run build-baseUrl well that raises questions. #32878 started preferring types over reference 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 Sheetal Nandi (@sheetalkamat) in #37928 (comment)

Activity

  1. sheetalkamat commented on Jul 24, 2020

    @sheetalkamat
    MemberAuthor

    Note that this is not regression since previous release. #32878 introduced this which is around for sometime now.

  2. sheetalkamat commented on Aug 10, 2020

    @sheetalkamat
    MemberAuthor

    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

  3. Griffork commented on Dec 7, 2020

    @Griffork

    This seems related to #34749 ? Presence of the baseUrl is breaking compiles in my project because ///reference path gets converted to an invalid ///reference types.

  4. 6 remaining items

  5. sheetalkamat commented on Nov 16, 2023

    @sheetalkamat
    MemberAuthor

    Duplicate of #34749

  6. locked as resolved and limited conversation to collaborators on Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugA bug in TypeScriptDuplicateAn existing issue was already createdRescheduledThis issue was previously scheduled to an earlier milestone

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions