Smaller changes tend to be safer and should break less. The less you change at one time, the better and less bugs which are easier to spot and fix. But if safe

Smaller changes tend to be safer and should break less. The less you change at one time, the better and less bugs which are easier to spot and fix. But if safety does not matter, or its pure crap anyway. Then refactor away. Proper review of core components that are used and proven is hard already, refactoring such components - don't do it if avoidable - there must be a very good reason. And convenience ain't one - you'll probably get some duplication of code and double maintainance during the transition period. Making small PR is just a way to be safe and smart, one branch with individual gradual commits that could be used separately is also a way (if they could be reviewed separatley).