OK, useful to know. I've not come across that library before. But of course I understand you can ship pre-built components, I was more thinking about the component dev stage. As you can also ship the compiler to the browser then that is the same as Vue and most of the other frameworks (Riot, Moon, etc.). Thanks for the information on this, very useful.
Indeed and if that is enabled by vue-custom-element without ES6/Webpack build then that would certainly be valuable. You can do the lazy loading code by hand of course but who wants to mess with that!
In my view, builds should always be optional.
Incidentally, and apologies to keep coming back to uibuilder - but npm installs and build stages are next on the list for uibuilder. To maintain maximum flexibility, uibuilder will look for a package.json in the folder structure containing your front-end files then look for a build script in that and execute it via npm. I will be extending the editor to allow editing of both the package.json and build configuration files in addition to the src files. This will allow the maximum flexibility, enable webpack/babel/etc but without forcing you down a specific set of tools. But I digress.
Agree. But I would point out that this won't, I don't think, necessarily be fixed by lazy loading or build steps. Some of this is the sheer size and complexity of Angular. On a mobile browser and even desktops, Angular often isn't that performant in my (limited) experience.
And of course, lazy loading, especially with charts and their need for historic data, can take itself an appreciable amount of time and may add complexity in trying to get the full dataset.
The efficiency and size of the admin ui is certainly something that probably needs keeping an eye on at least and I'm sure Nick and Dave and others are doing so. It would certainly be nice to keep it trim.
Indeed. We are all looking for this.