Skip to content

Commit 2f6710a

Browse files
committed
docs: clarify caveats for Vuetify config changes in dev
1 parent fb90d3f commit 2f6710a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/guide/configuration/vuetify-options.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,10 +6,10 @@ You can also use it in Nuxt Layers, the module will scan for `vuetify.config` fi
66

77
This module will watch Vuetify configuration files in development and only configuration files outside `node_modules`.
88

9-
When any Vuetify configuration file is changed in development, this module will invalidate all virtual configuration modules. The current version of the module will send 2 or 3 full page reloads in a row, not very optimal but much better than restarting the development server, we will try to fix it in future versions.
9+
::: warning CAVEATS
10+
Changing Vuetify configuration in development triggers a full page reload (sometimes 2-3) to invalidate virtual modules, avoiding a server restart. We aim to improve this in future versions.
1011

11-
::: warning
12-
When using external configuration files with SSR enabled, the module will restart the Nuxt dev server since Nuxt doesn't support HMR on the server: Vite 5.1 comes with the new `Vite Runtime API` as an experimental feature but Nuxt still not ready.
12+
With SSR and external configuration, the Nuxt dev server restarts due to lack of server-side HMR support in Nuxt.
1313
:::
1414

1515
For example, you can configure:

0 commit comments

Comments
 (0)