Yea, I wouldn't call them big either, but they happen none-the-less. For package developers it can be vital. Sometimes A must be loaded for B. It's mainly a third party javascript issue. The compatibility folder sometimes does the trick, but by contrast the same utility doesn't exist for package developers. It's a larger dependancy management issue not tackled by the current packaging system.