Open nwtn opened 10 years ago
It was mentioned a couple of times but we are at a point where this kind of functionality may do more harm than good. The size of the optimized is so small that splitting it may create bigger size since it would make CDN hosting more difficult.
There's no CDN hosting now, though, right?
Anyway, for me it's not entirely about size, but also about swapping out components. For example, if I want to use tablesaw instead of WET-BOEW's responsive tables, there (a) may be conflicts, and (b) will definitely be unused, redundant code.
Not right now but we want to get it to a CDN. I doubt that there would be conflicts because everything is very well encapsulated and plugins are only triggered when the right class is added so there is nothing stopping you from using an alternative solution.
Also, many plugins rely on external components that are only loaded as needed, therefore you wouldn't incur the size hit of those plugins if you don't use them.
A precursor to a build tool is to have and AMD/UMD build that can work out what components depend on each other. The second part of it is fully splitting out the SCSS sheets to consistently use variables for colours throughout the sheets.
I want to do this, but I haven't grokk'd RequireJS yet :frowning:
Has there been any discussion of a build tool that allows customization of components that are included? Something like Modernizr?