AggregateAssets weights should probably be affected by dependency

[jwebbdev]

The order of dependencies doesn't affect the files in aggregate assets. The issue this presents is with css. If I have a package dependent on my theme package, and I attempt to use a font that my theme has included the only way to ensure it is loaded is to set weights across packages, which seems like a bad way to handle it since a package you depend on may not have weights set already.

[BrockMcKean]

So, this is a huge problem that needs to be resolved through mean.json. If mean.json could provide a dependency tree configuration of mean packages that described the application (root of the dependency tree) and all of its dependent components (all other packages that it depends on), aggregation could be done in this order and be expected to work properly. Obviously, this would lead to specific patterns being chosen to do certain things and in some ways limit the freedom developers would have, but also would solve problems like these very easily in one swoop.

[timelf123]

This is related to https://github.com/linnovate/mean/issues/1429 and https://github.com/linnovate/mean/wiki/RC1.0-Core-Packages#unified-dependency-management