| > In addition, the API is designed with TypeScript type inference in mind. If I got that right, they plan a first-class TypeScript interface, and a second class Javascript one compiled from it. You choose whatever you want. Their problem is that you can not derive a good TypeScript interface from Javascript. But there is no problem on doing the reverse. None of that implies in any development-time or runtime requirement. > Top level APIs will likely receive an overhaul to avoid globally mutating the Vue runtime when installing plugins. That is a breaking change, yes. But not a large one. > We are breaking some internal functionalities into individual packages That is clearly not a breaking change. > The new codebase currently targets evergreen browsers only and assumes baseline native ES2015 support. That one implies on development-time requirements. They still can remove that requirement from the JS compiled distribution. |