Skip to content
This repository was archived by the owner on May 8, 2025. It is now read-only.

[Bug Report] Issue with using vue-cli-plugin-vuetify in a remote preset #338

Open
GinoVillalpando opened this issue Nov 3, 2022 · 1 comment

Comments

@GinoVillalpando
Copy link

Before I used to use vue-cli-plugin-vuetify in my vue-cli remote preset and it used to work fine but now I'm running into this error:

image

I noticed my preset is set to default and when using vue add vuetify I saw Default (recommended), Prototype (rapid development), and Configure (advanced) are no longer options since Vuetify 3 has been added.

If this has been updated is there documentation on what to put here to use Vuetify 2 - Vue CLI (recommended)?

Otherwise, I might have to just use vue add vuetify every time which isn't ideal.

here is my remote preset for reference:

{
  "useConfigFiles": true,
  "plugins": {
    "@vue/cli-plugin-babel": {},
    "@vue/cli-plugin-typescript": {
      "classComponent": true,
      "useTsWithBabel": true
    },
    "@vue/cli-plugin-router": {
      "historyMode": true
    },
    "@vue/cli-plugin-vuex": {},
    "@vue/cli-plugin-eslint": {
      "config": "prettier",
      "lintOn": ["save"]
    },
    "@vue/cli-plugin-unit-jest": {},
    "@vue/cli-plugin-e2e-cypress": {},
    "vue-cli-plugin-vuetify": {
      "preset": "default"
    }
  },
  "vueVersion": "2",
  "cssPreprocessor": "dart-sass"
}
@GinoVillalpando
Copy link
Author

This should be documented somewhere. My Vue preset was breaking with this plugin included and couldn't find out the source why until I found this commit: 4a2aa76 with the key being changed from preset -> install

This resolved my issue:

"vue-cli-plugin-vuetify": {
   "install": "default"
}

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant