import { defineUntypedSchema } from 'untyped' export default defineUntypedSchema({ experimental: { /** * Set to true to generate an async entry point for the Vue bundle (for module federation support). */ asyncEntry: { $resolve: (val) => val ?? false }, /** * Enable Vue's reactivity transform * @see https://vuejs.org/guide/extras/reactivity-transform.html * * Warning: Reactivity transform feature has been marked as deprecated in Vue 3.3 and is planned to be * removed from core in Vue 3.4. * @see https://github.com/vuejs/rfcs/discussions/369#discussioncomment-5059028 */ reactivityTransform: false, // TODO: Remove in v3.6 when nitro has support for mocking traced dependencies // https://github.com/unjs/nitro/issues/1118 /** * Externalize `vue`, `@vue/*` and `vue-router` when building. * @see https://github.com/nuxt/nuxt/issues/13632 */ externalVue: true, /** * Tree shakes contents of client-only components from server bundle. * @see https://github.com/nuxt/framework/pull/5750 */ treeshakeClientOnly: true, /** * Emit `app:chunkError` hook when there is an error loading vite/webpack * chunks. * * By default, Nuxt will also perform a hard reload of the new route * when a chunk fails to load when navigating to a new route. * * You can disable automatic handling by setting this to `false`, or handle * chunk errors manually by setting it to `manual`. * * @see https://github.com/nuxt/nuxt/pull/19038 * @type {false | 'manual' | 'automatic'} */ emitRouteChunkError: { $resolve: val => { if (val === true) { return 'manual' } if (val === 'reload') { return 'automatic' } return val ?? 'automatic' }, }, /** * Whether to restore Nuxt app state from `sessionStorage` when reloading the page * after a chunk error or manual `reloadNuxtApp()` call. * * To avoid hydration errors, it will be applied only after the Vue app has been mounted, * meaning there may be a flicker on initial load. * * Consider carefully before enabling this as it can cause unexpected behavior, and * consider providing explicit keys to `useState` as auto-generated keys may not match * across builds. * * @type {boolean} */ restoreState: false, /** * Inline styles when rendering HTML (currently vite only). * * You can also pass a function that receives the path of a Vue component * and returns a boolean indicating whether to inline the styles for that component. * * @type {boolean | ((id?: string) => boolean)} */ inlineSSRStyles: { async $resolve (val, get) { if (val === false || (await get('dev')) || (await get('ssr')) === false || (await get('builder')) === '@nuxt/webpack-builder') { return false } // Enabled by default for vite prod with ssr return val ?? true } }, /** * Turn off rendering of Nuxt scripts and JS resource hints. * You can also disable scripts more granularly within `routeRules`. */ noScripts: false, /** Render JSON payloads with support for revivifying complex types. */ renderJsonPayloads: true, /** * Disable vue server renderer endpoint within nitro. */ noVueServer: false, /** * When this option is enabled (by default) payload of pages generated with `nuxt generate` are extracted * * @type {boolean | undefined} */ payloadExtraction: undefined, /** * Whether to enable the experimental `` component for rendering content on the client * if there's an error in SSR. */ clientFallback: false, /** Enable cross-origin prefetch using the Speculation Rules API. */ crossOriginPrefetch: false, /** * Enable View Transition API integration with client-side router. * * @see https://developer.chrome.com/docs/web-platform/view-transitions */ viewTransition: false, /** * Write early hints when using node server. * * @note nginx does not support 103 Early hints in the current version. */ writeEarlyHints: false, /** * Experimental component islands support with and .island.vue files. * @type {true | 'local' | 'local+remote' | false} */ componentIslands: { $resolve: (val) => { if (typeof val === 'string') { return val } if (val === true) { return 'local' } return false } }, /** * Config schema support * * @see https://github.com/nuxt/nuxt/issues/15592 */ configSchema: true, /** * This enables 'Bundler' module resolution mode for TypeScript, which is the recommended setting * for frameworks like Nuxt and Vite. * * It improves type support when using modern libraries with `exports`. * * This is only not enabled by default because it could be a breaking change for some projects. * * See https://github.com/microsoft/TypeScript/pull/51669 */ typescriptBundlerResolution: { async $resolve (val, get) { if (typeof val === 'boolean') { return val } const setting = await get('typescript.tsConfig.compilerOptions.moduleResolution') if (setting) { return setting.toLowerCase() === 'bundler' } return false } }, /** * Whether or not to add a compatibility layer for modules, plugins or user code relying on the old * `@vueuse/head` API. * * This can be disabled for most Nuxt sites to reduce the client-side bundle by ~0.5kb. */ polyfillVueUseHead: false, /** Allow disabling Nuxt SSR responses by setting the `x-nuxt-no-ssr` header. */ respectNoSSRHeader: false, /** Resolve `~`, `~~`, `@` and `@@` aliases located within layers with respect to their layer source and root directories. */ localLayerAliases: true, /** Enable the new experimental typed router using [unplugin-vue-router](https://github.com/posva/unplugin-vue-router). */ typedPages: false, /** * Set an alternative watcher that will be used as the watching service for Nuxt. * * Nuxt uses 'chokidar-granular' by default, which will ignore top-level directories * (like `node_modules` and `.git`) that are excluded from watching. * * You can set this instead to `parcel` to use `@parcel/watcher`, which may improve * performance in large projects or on Windows platforms. * * You can also set this to `chokidar` to watch all files in your source directory. * * @see https://github.com/paulmillr/chokidar * @see https://github.com/parcel-bundler/watcher * @type {'chokidar' | 'parcel' | 'chokidar-granular'} */ watcher: 'chokidar-granular' } })