Skip to content

Cleanup handling of Closure Warnings #962

@thheller

Description

@thheller

Currently they are just logged once via shadow.build.closure/log-warnings but once cached they are gone. They are also kinda duplicated since JSInspector already runs into most of them and stores them in :js-warnings but that is never used. Don't know if :simple optimizations can generally find more or if parsing them via JSInspector already finds all.

Optimization warnings should be handled separately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions