Skip to content

Persistent incorrect semantic diagnostic after large rebase or checkout: Module has no exported member #47466

Closed
@MarcCelani-at

Description

@MarcCelani-at

Bug Report

When using tsserver in VSCode, I sometimes see persistent false error reports from diagnostics after a large rebase or checkout of the form, "Module '{}' has no exported member '{}'." The file mentioned in the error is a file that was updated in the checkout or rebase. Opening the file in question in VSCode loads the file and resolves the incorrect semantic diagnostic. Alternatively, restarting TSServer resolves the incorrect diagnostic

🔎 Search Terms

module has no exported member watch

🕗 Version & Regression Information

This has been happening as long as we can remember

🙁 Actual behavior

persistent incorrect ssemantic diagnostics

🙂 Expected behavior

No errors after a reasonable period of time

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugA bug in TypeScriptFix AvailableA PR has been opened for this issue

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions