I have a VueJS 3 project with which I want to use Vuetify 3 (^3.0.0-alpha.0), however, upon adding Vuetify I started getting dependency conflicts.
I also created a new empty VueJS 3 project with Vuetify 3 and got the same conflict.
I haven't modified package.json after the cli modifications on adding Vuetify 3 (https://next.vuetifyjs.com/en/getting-started/installation/).
I'm aware this is an alpha release but was wondering if it was something I was doing wrong on my end or if it's a bug and if so if there are any workarounds.
Updating all #vue/cli-service dependencies to their latest version as well as updating VuetifyJS 3 to the latest alpha solved this conflict.
Related
I was very happy with Vue 2 and VS Code, but with Vue 3 and Velur, I get this kind of issues:
You notice VoteBtn is imported and used above, but the linter complains. Is there a way to solve this?
I had the same issue because I had installed both Volar and Vetur.
Just remove Vetur and it will do the trick.
I'm following a tutorial to build a tinder clone using react native, for the styling I was using tailwind version 3.0.1 as this was the latest version at the time of the video, since finishing the basis of the project I decided to upgrade to the current version of tailwind to make use of all the new styling features, however upon running yarn uninstall tailwind-rn#3.0.1 and then yarn add tailwind-rn and after upgrading to the proper syntax (you now need to import {useTailwind} instead of {tailwind} and you must put const tailwind = useTailwind(); at the start of your code) I'm presented with this mess as the homepage which apparently now has no styling at all, how can I fix this, here is screenshots of before and after upgrading to the latest version of tailwind:
before:
after:
When I started a new Vue project with Quasar, it installed the latest version of Vue which is 3.2.33, however I want to use 3.2.30.
How can I roll back or change it to that version of Vue?
You can fix a specific version to be used via the following in your package.json
{
"dependencies": {
"vue": "3.2.30"
},
}
Regarding the Quasar CLI, it creates a project with the following by default
Regarding semver, since it's ^3.0.0, the range will be >=3.0.0 and <4.0.0.
So every news project built by Quasar will be using the stable MAJOR v3 and the latest MINOR + PATCH versions.
You cannot change that properly.
(you could of course hack it yourself by keeping your own frozen version of Quasar or risk to edit it in your yarn.lock but I heavily recommend against that)
At the end, the project may use something lately released by the Vue core team or a critical fix. If the dev team of Quasar requires this change but you hacked it, you may experience some weird bugs that you will have no idea of the source (on top of other possible conflicts/issues).
TLDR: use the latest version of Vue (as intended by the Quasar team) or maybe lock a specific version of quasar that is fitting your needs regarding the Vue version.
You will not risk anything doing that.
PS: Quasar ^1.0.0 is used for Vue2 apps. If you want to see if some specific versions of Quasar are running some specific frozen versions of Vue, you can always dig deep into the releases of the project.
I'm trying to migrate a Vue2 project from Vue-CLI/Webpack to Vite. This migration guide says #vitejs/plugin-vue should be added as a dev dependency, but I'm not sure if I really need it, or if I do, which version I should use?
The documentation on GitHub doesn't say much about what this plugin is for, or when it should be installed.
#vitejs/plugin-vue is for Vue 3. You can use vite-plugin-vue2 for Vue 2.
I made a sample project with Vite, Vue2 and TailwindCSS that you can test / fork on stackblitz.
https://stackblitz.com/edit/vitejs-vite-hu1crh
I want to use vuesax on my first project and I fell in love with vuesax components. I am actually using Vue cli 2.
Which version of Vue is required by vuesax?
vuesax 3.x and 4.x depend on Vue 2.
So vuesax projects need the latest version of Vue 2 in your project (currently 2.6.14):
npm i -S vue#2