If, for some reason, you need in-browser template compilation even with a build step, you can do so by configuring the build tool to alias vue to vue/dist/ instead. Our default tooling setups use the runtime-only build since all templates in SFCs are pre-compiled. However, they will increase the payload by ~14kb. runtime are full builds: they include the compiler and support compiling templates directly in the browser.

When using these builds, all templates must be pre-compiled via a build step.īuild files that do not include. To reduce client bundle size, Vue provides different 'builds' optimized for different use cases.īuild files that start with vue.runtime.* are runtime-only builds: they do not include the compiler. On the other hand, the compiler would be unnecessary if we pre-compile the templates with a build step.

In such cases, Vue needs to ship the template compiler to the browser in order to perform on-the-fly template compilation. When using Vue without a build step, component templates are written either directly in the page's HTML or as inlined JavaScript strings. Note on In-Browser Template Compilation Tools / Plugins that help with auto migration.Vue CLI -> Vite Migration Guide from VueSchool.io.Vite will provide superior developer experience in most cases.įor information on migrating from Vue CLI to Vite: It is now in maintenance mode and we recommend starting new projects with Vite unless you rely on specific webpack-only features. Vue CLI is the official webpack-based toolchain for Vue. To configure Vue-specific behavior in a Vite project, for example passing options to the Vue compiler, check out the docs for online playgrounds mentioned above also support downloading files as a Vite project.

To learn more about Vite, check out the Vite docs.

$ npm init command will install and execute create-vue, the official Vue project scaffolding tool.

Webstorm cost