Skip to content

Build a test for checking built size #3052

Description

@RoboErikG

There are two things that need to be done for this.

First is just building a test for Blockly's compiled size and gzipped size so we can track the overall size of the library over time.

Second, we now have a way to remove optional components from Blockly at build time via the requires.js file. We should build a test that generates the bytes saved by removing each component so developers can decide which components are worth using for their application.

See #3023 for a partial list of components that may be optional over time.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    • Status
      Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions