Skip to content

Type declarations don't match runtime export #5

@macieklamberski

Description

@macieklamberski

Hi there! While wanting to migrate to the new split parser/builder packages, I've noticed inconsistency in the type definitions.

This makes it impossible to import correctly - named import type-checks but crashes at runtime, default import works at runtime but fails type-checking.

The fix would be to choose either named or default export and use in both places. Happy to submit a PR for whichever direction you prefer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions