The directory containing your static files, which will be directly accessible via the Nuxt server and copied across into your dist folder when your app is generated. The plugins directory, each file of which will be auto-registered as a Nuxt plugin.

The directory which will be processed to auto-generate your application page routes. The modules directory, each file in which will be auto-registered as a Nuxt module. The middleware directory, each file of which will be auto-registered as a Nuxt middleware. The layouts directory, each file of which will be auto-registered as a Nuxt layout. The assets directory (aliased as ~assets in your build). It is better to stick with defaults unless needed. dirĬustomize default directory structure used by Nuxt. Breaking changes for devtools might not reflect on the version of Nuxt. This should not be set directly as it will always be overridden by the dev server with the full URL (for module and internal use). Set to true to enable bundle analysis, or pass an object with options: for webpack or for vite. Nuxt uses webpack-bundle-analyzer to visualize your bundles and how to optimize them. It will be merged with app.config file as default value. appConfigįor programmatic usage and type support, you can directly provide app config with this option. Only JSON-serializable values are allowed.Ĭustomize Nuxt root element tag. This can be overridden with definePageMeta on an individual page. Default values for KeepAlive configuration between pages.

Discord nitro code generator javascript