This template should help get you started developing mobile applications with Vue3 and Typescript and Vant in Vite.
yarn install
yarn start
yarn build
yarn lint
yarn generate
Vant uses px unit by default,You can use tools such as postcss-pxtorem to transform px unit to rem unit.
PostCSS config example:
// .postcssrc.js
module.exports = {
plugins: {
'postcss-pxtorem': {
rootValue: 37.5,
propList: ['*'],
},
},
};you can use tools such as postcss--px-to-viewport to transform px unit to viewport units (vw, vh, vmin, vmax).
PostCSS config example:
// .postcssrc.js
module.exports = {
plugins: {
'postcss-px-to-viewport': {
viewportWidth: 375,
},
},
};If the size of the design draft is 750 or other sizes, you can adjust the rootValue to:
// .postcssrc.js
module.exports = {
plugins: {
// postcss-pxtorem version >= 5.0.0
'postcss-pxtorem': {
rootValue({ file }) {
return file.indexOf('vant') !== -1 ? 37.5 : 75;
},
propList: ['*'],
},
},
};VSCode + Vetur. Make sure to enable vetur.experimental.templateInterpolationService in settings!
<script setup> is a feature that is currently in RFC stage. To get proper IDE support for the syntax, use Volar instead of Vetur (and disable Vetur).
Since TypeScript cannot handle type information for .vue imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in .vue imports (for example to get props validation when using manual h(...) calls), you can use the following:
Run Volar: Switch TS Plugin on/off from VSCode command palette.
- Install and add
@vuedx/typescript-plugin-vueto the plugins section intsconfig.json - Delete
src/shims-vue.d.tsas it is no longer needed to provide module info to Typescript - Open
src/main.tsin VSCode - Open the VSCode command palette
- Search and run "Select TypeScript version" -> "Use workspace version"