If you are a former Webflow client… you don’t have the ability to “fix the problem” without becoming a Webflow customer again (which means out-of-pocket-money)
@Revolution That’s not the case at all - this post shows steps on how to resolve this by a search-replace in your exported code, without having to go to Webflow or pay anything.
To your broader question - unfortunately it’s very hard to predict what 3rd parties will do in the future. For example, it’s theoretically possible that Google will decide that providing Google Fonts for free is no longer in their best interests, or Typekit could go out of business, or Vimeo could decide to start charging for all embed traffic. That would be terrible for the web, and those scenarios are very unlikely to ever happen, but there’s just no way to guarantee that these external dependencies will never change. It’s a fact of life on the web that browsers change, libraries get deprecated, old CDNs disappear, 3rd party services change, etc - and sometimes that does require manual effort to fix. At Webflow, our goal is to shield you from as much of that manual effort as possible, but we can’t guarantee that it will never happen. I hope that makes sense.