Skip to content

TS 5.0 - ModuleResolutionKind Enum changed (breaking change that's not listed) #53131

Closed

Description

@dummdidumm

Bug Report

ts.ModuleResolutionKind seems to have changed between 4.9 and 5. The enum now has a Node10 value which I guess is the old NodeJs. This isn't mentioned in the API breaking changes list, so this is either a bug (which will probably break a few libraries [for example the rollup typescript plugin, through which I discovered this]) or should be added to that list.
(for me personally, if you want to keep the name change, it would be best to first deprecate the old name and remove it later)

🔎 Search Terms

ModuleResolutionKind

🕗 Version & Regression Information

  • This changed between versions 4.9 and 5.0

⏯ Playground Link

Doesn't apply here

💻 Code

ts.ModuleResolutionKind.NodeJs

🙁 Actual behavior

Error

🙂 Expected behavior

No error

Activity

  1. jakebailey commented on Mar 7, 2023

    @jakebailey
    Member

    NodeJs was changed to Node10 in #51901, and I'm also noticing some cross-linked changes to that PR of people working around this.

    Andrew Branch (@andrewbranch) Should we have left behind a deprecated enum member?

    (It is of course 5.0 where we made loads of breaking changes, so we could just document it.)

  2. andrewbranch commented on Mar 7, 2023

    @andrewbranch
    Member

    I may have meant to make it a breaking change; I don’t remember. But it’s very easy to make it backward-compatible. It’s probably best to add NodeJs back.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScriptDomain: APIRelates to the public API for TypeScript

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions