Skip to content

Checker: error when named import does not exist in module #976

@milkyskies

Description

@milkyskies

When importing a named export that doesn't exist in a module (e.g. import { Markdown } from "react-markdown" when the package only has a default export), the compiler should error instead of silently generating broken code.

Currently requires tsgo to resolve npm package exports. Without tsgo, all npm imports are unresolved and the checker can't verify they exist.

Blocked by tsgo integration for npm packages.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions