Ever since we announced Vite+, the excitement, and the questions, have been rolling in. We took some time to answer the most common ones: How do frameworks benefit from Vite+? Vite+ is an integration on the application-level. Frameworks don't need to rewrite their internals for developers to benefit. They can provide Vite+ plugins for a smoother developer experience (DX) and tighter integration, but they won't have to switch to Vite+ themselves. Open-source framework repositories can use Vite+ themselves for free in their own development workflows. Is Vite paid software now? No. @vite_js remains free and open-source under the MIT license. We stated from the beginning that all code and packages released as open-source will remain open-source. Vite+ is a separate product that provides additional features and services as a superset of Vite to provide an end-to-end JavaScript tooling solution. What impact will Vite+ have on Vite and other open-source projects? Vite+ is built on top of the existing open-source ecosystem, and can only function if that ecosystem is healthy. As a paid product, Vite+ supports the sustainability of the underlying open-source projects it builds on. Can I use Vite+ with my own tooling? Yes. Vite+ aims to give the best DX and performance but does not force you to use only Vite+ tools and commands. Its task runner and caching will work with arbitrary tasks, not just with built-in Vite+ commands. Questions left? Drop them below 👇