Skip to content

Tree-shaking and secondary entry points #93

Open
@hakimio

Description

@hakimio

Right now angular-odata takes almost 200KB in our initial production bundle chunk. Far exceeding any other libraries in size.
Is there any way to make angular-odata modular and introduce secondary entry points to make it tree-shakable?
Schema loading logic maybe could be separated?

image

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