This is a bad idea. First, if the modules are already separate from the core, there's no reason not to go one step further and make them separate downloads too.
Well, there are reasons for doing so, and there are reasons for not doing so.
I think (or i hope) you will agree that it is not a good idea to make a module for a topleft corner indicator, a module for a topright corner indicator, a bottomleft corner indicator, ... eaven if there are maybe a handfull users that won't use them. And i bet it would be no problem to seperate all this.
Question is: is it worth to do so?
Quote fromSecond, if you package 5, 10, or 50 plugins with the core in the same download, then every time any one of those is updated, users will have to download the entire package, even if the change merely corrected a single typo in a single file; this is a waste of everyone's time and bandwidth.
If something isn't included in the core, there's a reason for it... maybe you think Lifebloom tracking is a good candidate for bundling, but why should anyone other than resto druids have to download this plugin and waste even a single byte storing it? For anyone else, it's totally useless.
I agree, except for the "single byte" thing.
It's also a waste of bandwith and space to have every WAU user get a long list of packages everytime if the package content is very small. I don't know where to draw the line, but having a seperate module for something that is smaller than a certain amount of code or so, you waste more bandwith than you safe.
I could imagine that this amount would be somewhere around 1kb or so, but this is just a guess, there are smarter people out than me...