Skip to content

Overly aggressive tree-shaking #440

Description

@Rich-Harris

While working on #435, realised that the mechanism for tracing which code gets run as part of a module's initial evaluation fails with what we might refer to as complex call expressions: one, two. Not immediately sure what the best solution looks like.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions