That strategy sucks when you have 15 supercomponents depending on 1 subcomponent, you want to rewrite the subcomponent, and now you have to deal with all 15 of them and get codeowners approvals from all 15 of those teams.
In a polyrepo org you just release version 2.0 of the subcomponent and upgrade the 1-2 of the 15 teams where the 2.0 features are actually needed now. The rest of the users can upgrade on their own schedule.
In a polyrepo org you just release version 2.0 of the subcomponent and upgrade the 1-2 of the 15 teams where the 2.0 features are actually needed now. The rest of the users can upgrade on their own schedule.