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?
Right now
angular-odatatakes almost 200KB in our initial production bundle chunk. Far exceeding any other libraries in size.Is there any way to make
angular-odatamodular and introduce secondary entry points to make it tree-shakable?Schema loading logic maybe could be separated?