This is a starter project that uses Vuetify as the UI framework. Please use scss version 1.32.12 due to a problem on the Vuetify side.
Vuetify3 version is here.
This template is for using Vue2 with TypeScript in Vite. Includes vue-router and Vuex, vue-property-decorator.
In addition, ESLint, Stylelint, and Prettier are also included and are set to be executed automatically at runtime and commit. (Since these settings are set strictly, please relax yourself.)
Also, when the development server is executed, it is checked in real time by vite-plugin-checker.
It also supports the Composition API. The installed VueRouter and Vuex are for Vue2, but you can use the functions (such as useRouter(), useRoute() and useStore()) for the composition API for Vue3.
Of course, Vuetify instance can also be accessed with useVuetify(). In the Composition API, you can handle it in the same way as this.$vuetify by entering const vuetify = useVuetify(); in the setup() function.
It is possible to mix code written in Composition API and code written in vue-property-decolator, but it is not recommended to use them together in the same component. 1
As a limitation, Vue2's composition api cannot monitor the router with the watch function. In that case, monitor it by the following normal method:
watch: {
$route: {
handler(to) {
//
},
immediate: true,
},
},If you are thinking of supporting Vue2 and Vue3 both, consider introducing vue-demi.
If you want to use vue-i18n, please install vue-i18n-composable and call the instance with useI18n().
In addition, the conventional method using $t() written in non composition-api can be used as it is.
VSCode + Volar (and disable Vetur).
| Command | Description |
|---|---|
| dev | Start devserver. |
| clean | Clear devserver cache. |
| lint | Run ESLint and prettier. |
| lint:style | Run Stylelint. |
| lint:markup | Check vue markup. |
| build | Build for production. |
| build:analyze | Execute Bundle Analyzer |
| build:deploy | Build for production without checking. |
| build:clean | Clear production build files. |
| preview | Run the program generated by the production build. |
It also works when migrating from VueCLI.
However, when importing a stylesheet with @import, it cannot be specified from the library directory. Must be specified from ~node_modules/.
Also, if you used the .env file in the previous environment, you need to change the calling part from process.env to import.meta.env after installing vite-plugin-env-compatible separately.
When adding or deleting files, an error may occur and even if the error is corrected, it may not be reflected in devserver. In that case, stop devserver and delete all the files in the node_modules/.vite directory. You can also run it with the clean command.