angular-odata icon indicating copy to clipboard operation
angular-odata copied to clipboard

Tree-shaking and secondary entry points

Open hakimio opened this issue 1 year ago • 0 comments

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

hakimio avatar Sep 26 '24 11:09 hakimio