It's unbelievable that this is still not a thing. I'm seriously starting to evaluate other Blazor UI libraries like Syncfusion even though I know the switch over would have a significant amount of rewriting and adjusting to the new library. But, when the "other side" offers things like https://www.syncfusion.com/blazor-components/blazor-datagrid separate js downloads for each component, I'm contemplating the switch.

And to Nadezhda and others saying the pay for the Telerik libraries is not that big: the Telerik library is LITERALLY the single most time consuming thing in a Blazor apps startup. With a 4x CPU slowdown simulating a mobile device, 1.3 seconds is attributed to evaluating your javascript

Also a quick Excel calculation of the payload sizes from a non-cached reload of a mediumish Blazor app comes out to these sizes in this case. Telerik representing everything with Telerik in the url and System all that had Microsoft, dotnet, etc. in the url. So we can clearly see that both Teleriks wasm and javascript VASTLY outsize ALL OF the dotnet runtime that is loaded. Really let that sink in, a single component library, from which I might need 3-5 components for an app has a larger payload (and therefore longer parsing and compiling times) than all of dotnet.

And of course, with every release when Telerik adds more components and more AI this problem only gets worse! The payload and parse+compile times will ONLY keep increasing. This split up should've been done 5 years ago, not telling clients to "hey, you can build your own custom payload for components you might use. And you get to tweak it every time an app that uses it adds another component! Oh and when Telerik updates, you get to update this monster aswell!"

Is there a simple way on how I can analyse the files and know the dependencies of each components? I've read your workaround but it's not as simple as what is written there. It's more like a trial and error game and it is time consuming.

I might try to build a little tool to extract the import/export commands and build a dependency tree.

Thank you for the update. :)

This feature would be great for public facing Blazor Webassambly applications, where the initial download is quite large.

An example of what I am talking about doing refers to loading only the JavaScript required for the component on the screen.  So, we don't have to load the entire Telerik Blazor library if we are only looking using a couple components.

 

So, if loading the "ToolBar" only load the JavaScript required for the toolbar control. This could be imported on control render.