You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 8, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on May 8, 2025. It is now read-only.
I'm trying out the rally preset. It has a lighter background color from the default dark theme. After I comment out the preset usage in the vuetify.js file, the background color remains the same.
import Vue from 'vue';
import Vuetify from 'vuetify/lib';
//import { preset } from 'vue-cli-plugin-vuetify-preset-rally/preset'
Vue.use(Vuetify);
export default new Vuetify({
//preset,
theme: {
dark: true
}
});
Also, I need to manually remove the font link from the index.html. How can I disable these material design study themes? And how can I use a custom background color?
For anyone wondering what they can do though I found that if you remove the preset from your package.json dev section and then delete your node_modules directory and you may need to delete the package.lock file, then run yarn install again it will 'revert' the changes.
I've been playing around with the Vuetify presets to weigh if creating a custom preset is a good idea. Spinning up new projects via vue create, vue add vuetify, and finally vue add vuetify-preset-{name}... I am seeing the same behavior. The preset's variables seem to "stick" even when preset is no longer passed as part of the project's Vuetify bootstrapping. Has anyone figured out why this is? All I can figure is that it has something to do with how Vue and/or Vuetify plugins are registered via add. I appreciate others posting about this. 👍
Activity
michaeltoohig commentedon Jun 6, 2020
Same.
For anyone wondering what they can do though I found that if you remove the preset from your
package.jsondev section and then delete yournode_modulesdirectory and you may need to delete thepackage.lockfile, then runyarn installagain it will 'revert' the changes.JessicaOPRD commentedon Nov 2, 2020
I've been playing around with the Vuetify presets to weigh if creating a custom preset is a good idea. Spinning up new projects via
vue create,vue add vuetify, and finallyvue add vuetify-preset-{name}... I am seeing the same behavior. The preset's variables seem to "stick" even whenpresetis no longer passed as part of the project's Vuetify bootstrapping. Has anyone figured out why this is? All I can figure is that it has something to do with how Vue and/or Vuetify plugins are registered viaadd. I appreciate others posting about this. 👍