[qualsiasi]

It's not different at all, but you might not want to add this "breaking" scenario to any component in your app, or you might accept the risk - up to you.

If you accept the risk for any component to break you'll eventually end-up spending your time fixing something other people broke, offering a poor experience to your end customer.

Mind that in corporate environments getting authorized as a software supplier to deploy an update could take weeks if not months, in the meanwhile the customer perspective is that "your product broke" (and made them lose money) - this is why I like to ship as many dependencies as possible in the final bundle.

This is my opinion, maybe biased by the market sector I'm working in. Not saying it should work the same way for everyone, just my 2c.