\n\n3) Navigate to `pages/index.vue`, modify the `console.log()` and save\n\n### Describe the bug\n\nThe previous [issue](https://github.com/nuxt/nuxt/issues/25214) was closed, but the error remains even in the latest Nuxt version.\n\nThe error will disappear if you add `lazy:true` option\n\n```\nconst { data } = await useFetch('https://jsonplaceholder.typicode.com/todos/1', {\n lazy: true\n})\n```\n\nAs you can see, both `app.vue` `layouts/default.vue` are wrapped with `divs` as it was suggested in the previous issue but we still get the bug.\n\nIs adding `lazy` option is the best workaround as for now?\n\n\u003Cimg width=\"500\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ca5929e7-f84b-4d0f-a57b-e1cf38c34813\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nvirtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16 [Vue warn]: Unhandled error during execution of component update \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage> \n at \u003CDefault ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CAsyncComponentWrapper ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js:51\nlogError @ runtime-core.esm-bundler.js:263\nhandleError @ runtime-core.esm-bundler.js:255\ncallWithErrorHandling @ runtime-core.esm-bundler.js:201\nflushJobs @ runtime-core.esm-bundler.js:408\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js:322\nqueueJob @ runtime-core.esm-bundler.js:317\neffect2.scheduler @ runtime-core.esm-bundler.js:5448\ntrigger @ reactivity.esm-bundler.js:253\nendBatch @ reactivity.esm-bundler.js:311\nnotify @ reactivity.esm-bundler.js:597\ntrigger @ reactivity.esm-bundler.js:571\nset value @ reactivity.esm-bundler.js:1448\nfinalizeNavigation @ vue-router.mjs:3498\n(anonymous) @ vue-router.mjs:3363\nPromise.then\npushWithRedirect @ vue-router.mjs:3330\npush @ vue-router.mjs:3255\nreplace @ vue-router.mjs:3258\naddRoutes @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16\n(anonymous) @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:21\n(anonymous) @ client:34\n(anonymous) @ client:208\n(anonymous) @ client:183\nqueueUpdate @ client:183\nawait in queueUpdate\n(anonymous) @ client:884\nhandleMessage @ client:882\nonMessage @ client:299\n(anonymous) @ client:429\ndispatchEvent @ .localservice@runtime.5a421e5b.js:26\n_handleMessage @ .localservice@runtime.5a421e5b.js:26\n_0x3963e2 @ .localservice@runtime.5a421e5b.js:26Understand this warningAI\nruntime-dom.esm-bundler.js:51 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\n at parentNode (runtime-dom.esm-bundler.js:51:30)\n at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5410:11)\n at ReactiveEffect.run (reactivity.esm-bundler.js:225:19)\n at ReactiveEffect.runIfDirty (reactivity.esm-bundler.js:263:12)\n at callWithErrorHandling (runtime-core.esm-bundler.js:199:33)\n at flushJobs (runtime-core.esm-bundler.js:408:9)\n```",[2856,2859,2862,2865],{"name":2857,"color":2858},"dx","C39D69",{"name":2860,"color":2861},"bug","d73a4a",{"name":2863,"color":2864},"vite","3574D1",{"name":2866,"color":2867},"🔨 p3-minor","FBCA04",31493,"nuxt","open","TypeError: Cannot read properties of null (reading 'parentNode') with useFetch","2025-03-21T17:04:23Z","https://github.com/nuxt/nuxt/issues/31493",0.6842301,{"description":2876,"labels":2877,"number":2888,"owner":2869,"repository":2869,"state":2870,"title":2889,"updated_at":2890,"url":2891,"score":2892},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.1\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-yn4nmm?file=plugins/test.ts\r\n\r\n### Describe the bug\r\n\r\nWhen passing the `ctx.options` of a $fetch onResponse to another $fetch generates types incompatibility, I had this problem since 3.2 but still is not fixed:\r\n\r\n```\r\nArgument of type '{ onResponse: undefined; baseURL?: string | undefined; body?: BodyInit | Record\u003Cstring, any> | null | undefined; params?: SearchParameters | undefined; ... 19 more ...; window?: null | undefined; }' is not assignable to parameter of type 'NitroFetchOptions\u003CRequestInfo, \"delete\" | \"get\" | \"post\" | \"head\" | \"patch\" | \"put\" | \"connect\" | \"options\" | \"trace\">'.\r\n Types of property 'method' are incompatible.\r\n Type 'string | undefined' is not assignable to type '\"delete\" | \"get\" | \"post\" | \"GET\" | \"HEAD\" | \"PATCH\" | \"POST\" | \"PUT\" | \"DELETE\" | \"CONNECT\" | \"OPTIONS\" | \"TRACE\" | \"head\" | \"patch\" | \"put\" | \"connect\" | \"options\" | \"trace\" | undefined'.\r\n Type 'string' is not assignable to type '\"delete\" | \"get\" | \"post\" | \"GET\" | \"HEAD\" | \"PATCH\" | \"POST\" | \"PUT\" | \"DELETE\" | \"CONNECT\" | \"OPTIONS\" | \"TRACE\" | \"head\" | \"patch\" | \"put\" | \"connect\" | \"options\" | \"trace\" | undefined'.ts(2345)\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2878,2881,2884,2887],{"name":2879,"color":2880},"discussion","538de2",{"name":2882,"color":2883},"types","2875C3",{"name":2885,"color":2886},"workaround available","11376d",{"name":2857,"color":2858},20287,"[types] $fetch.onResponse(ctx)","2024-06-30T11:09:03Z","https://github.com/nuxt/nuxt/issues/20287",0.6892708,{"description":2894,"labels":2895,"number":2899,"owner":2869,"repository":2869,"state":2870,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v20.10.0`\n- Nuxt Version: `3.17.4`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `yarn@1.22.19`\n- Builder: `-`\n- User Config: `future`, `compatibilityDate`, `experimental`, `features`, `unhead`, `modules`, `eslint`, `components`, `primevue`, `shadcn`, `colorMode`, `dayjs`, `veeValidate`, `app`, `nitro`, `runtimeConfig`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `@vueuse/nuxt@13.2.0`, `@nuxtjs/tailwindcss@6.14.0`, `@headlessui-float/nuxt@0.15.0`, `@primevue/nuxt-module@4.3.4`, `dayjs-nuxt@2.1.11`, `shadcn-nuxt@2.1.0`, `@nuxtjs/color-mode@3.5.2`, `@vee-validate/nuxt@4.15.0`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-glf1dfbb?file=nuxt.config.ts\n\nOpen `useMyData.ts` and check the `res` type. It should be `AsyncData\u003Cstring | null, ...>`, but it is `AsyncData\u003Cstring | undefined, ...>` desipte the fact that `experimental.defaults.useAsyncData.value` is set to `'null'` in `nuxt.config.ts.`.\n\nAlso please check `.nuxt/types/app.defaults.d.ts` file, that shows that the type is really `undefined` (`type DefaultAsyncDataValue = undefined`).\n\n### Describe the bug\n\nWhen `future.compatibilityVersion` is set to `4` and `experimental.defaults.useAsyncData.value` is set to `'null'` then `useAsyncData` and `useFetch` use `null` as the default. This works in runtime as expected.\n\nBut the type of `DefaultAsyncDataValue` generated in `.nuxt/types/app.defaults.d.ts` is still `undefined`. I thought the whole point of introduction of `DefaultAsyncDataValue` type was to make this change backward compatible.\n\nI even found a template in #27294 that supposedly should be responsible for this: https://github.com/nuxt/nuxt/pull/27294/files#diff-2176c7ab69dcd5ffc94e79963693b007471788f25591aeb72e7533240ebad2c2\n\nBut it looks like it doesn't take into account `experimental.defaults.useAsyncData.value` flag.\n\nAll the above also applies to `experimental.defaults.useAsyncData.errorValue` flag.\n\n### Additional context\n\nI'm not sure if this option was ever intended to modify TypeScript definitions. Maybe I'm expecting too much. :D\n\nBut I would say the option is really useful during migration, IMHO. While the Nuxt migration docs mentions `npx codemod@latest nuxt/4/default-data-error-value`, in my case this command didn't catch any comparisons to `null` in the codebase. But they really exists, so the code starts to work incorrectly when `useFetch` suddenly starts to return `undefined` instead of the expected `null`.\n\nHonestly, I'm surprised that this change is marked as \"Impact Level: Minimal\". It is pretty severe impact to me, if code's expectations have been changed. :)\n\nFor example I found a code like this:\n\n```ts\nconst { data: loadedItems } = await useItemDictionary() // Uses useFetch + cache under the hood\nconst items = computed(() => {\n if (loadedItems.value === null) {\n return []\n }\n return loadedItems.value.map(\n (item) => ...\n )\n})\n```\n\nPreviously it worked, but now it will throw an error because it will try to use `Array.map` on `undefined`.\nThe `codemod` didn't catch this error.\n\nFortunately, this error was catched by TypeScript. But it catches it even when `experimental.defaults.useAsyncData.value` is set to `'null'`, while it shouldn't. :) Quite contrary, if you chage `loadedItems.value === null` to `loadedItems.value === undefined` in the code above, the TypeScript error will disappear, but runtime error will appear, if `experimental.defaults.useAsyncData.value` is set to `'null'`.\n\n### Logs\n\n```shell-script\n\n```",[2896],{"name":2897,"color":2898},"pending triage","E99695",32213,"Setting `experimental.defaults.useAsyncData.value` does not update TS types","2025-05-27T01:19:10Z","https://github.com/nuxt/nuxt/issues/32213",0.6930146,{"description":2905,"labels":2906,"number":2916,"owner":2869,"repository":2869,"state":2917,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.0\r\n- Package Manager: bun@1.0.29\r\n- Builder: -\r\n- User Config: app, devtools, modules, build, sourcemap, runtimeConfig, css, imports\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @unocss/nuxt@0.58.5, @vueuse/nuxt@10.9.0\r\n- Build Modules: -\r\n```\n\n### Reproduction\n\n```\r\nconst { data: testData } = useAsyncData\u003C{ id: 1, name: string }[] | null>('some', () => $fetch('/api/some'))\r\ntype TestDataType = MaybeRef\u003Cany[] | null>\r\ntype TestGeneric\u003CT extends TestDataType> = T extends MaybeRef\u003Cinfer U> ? U : T\r\ntype Test = TestGeneric\u003Ctypeof testData>\r\n```\r\n\r\n\r\n\r\n\n\n### Describe the bug\n\nIt was all fine till yesterday I think,\r\nI ran package updates, then this happenes.\r\nIt also happens on vueuse's some functions.\r\n\r\nAny ref types that goes into generic or function arg throws this error about [RefSymbol]\r\n\r\n```\r\nType 'Ref\u003C{ id: 1; name: string; }[] | null>' does not satisfy the constraint 'TestDataType'.\r\n Property '[RefSymbol]' is missing in type 'Ref\u003C{ id: 1; name: string; }[] | null>' but required in type 'Ref\u003Cany[] | null>'.ts(2344)\r\nreactivity.d.ts(420, 5): '[RefSymbol]' is declared here.\r\n```\n\n### Additional context\n\nI see vue's last update is from 20 hours ago,\r\nso I did \r\nnuxi cleanup\r\nremoved all the caches and lockfile of package manager\r\nremoved node_modules\r\nand re installed with vue 3.4.20,\r\nbut it wasn't fixed.\n\n### Logs\n\n_No response_",[2907,2910,2911,2914],{"name":2908,"color":2909},"3.x","29bc7f",{"name":2897,"color":2898},{"name":2912,"color":2913},"upstream","E8A36D",{"name":2915,"color":2867},"needs reproduction",26009,"closed","typescript error on Ref type","2024-03-04T10:26:04Z","https://github.com/nuxt/nuxt/issues/26009",0.6740744,{"description":2923,"labels":2924,"number":2929,"owner":2869,"repository":2869,"state":2917,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-z6juqt?file=components%2FTest.vue\r\n\r\n`npm run typecheck` in terminal\r\n\r\n```\r\ncomponents/Test.vue:8:17 - error TS2339: Property 'optionalStr' does not exist on type 'CreateComponentPublicInstanceWithMixins\u003CToResolvedProps\u003C{}, {}>, {}, {}, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, {}, VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly\u003C...> & Readonly\u003C...>, ... 16 more ..., {}>'.\r\n\r\n8 \u003Cspan v-if=\"optionalStr\">{{ optionalStr }}\u003C/span>\r\n ~~~~~~~~~~~\r\n```\n\n### Describe the bug\n\nAfter upgrading from Nuxt 3.12.3 to 3.13.2, these TS errors showed up in every component that only uses optional props. The error disappears if we add a single required prop or enable TS strict mode.\n\n### Additional context\n\nThe issue doesn't seem to be present in a pure Vue/Vite project:\r\n\r\nhttps://stackblitz.com/edit/vitejs-vite-ece16d?file=src%2Fcomponents%2FHelloWorld.vue\n\n### Logs\n\n_No response_",[2925,2926],{"name":2897,"color":2898},{"name":2927,"color":2928},"possible regression","B90A42",29041,"Components with only optional props lose props type if strict mode is disabled","2024-09-23T10:12:23Z","https://github.com/nuxt/nuxt/issues/29041",0.6744085,{"description":2935,"labels":2936,"number":2939,"owner":2869,"repository":2869,"state":2917,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.1\r\n- Nitro Version: 2.3.3\r\n- Package Manager: npm@7.17.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-voetqy?file=components/VTest.vue\n\n### Describe the bug\n\nTrying to define a component's properties using an empty interface that extends another interface fails using `withDefaults(defineProps\u003CProps>(), { ... }` \n\n### Additional context\n\nCould be an issue in vuejs/core since [this](https://github.com/vuejs/core/issues/4498) and [this](https://github.com/vitejs/vite/issues/5437) exist, but it was fixed in Vue 3.2.42 (2022-11-09).\n\n### Logs\n\n```shell-script\n[plugin:vite:vue] Transform failed with 1 error:\r\n/home/projects/github-voetqy/components/VTest.vue:10:26: ERROR: Unexpected \"}\"\r\n/home/projects/github-voetqy/components/VTest.vue:10:26\r\nUnexpected \"}\"\r\n8 | expose();\r\n9 | \r\n10 | const props = __props as };\r\n | ^\r\n11 | \r\n12 |\r\n at failureErrorWithLog (file:///home/projects/github-voetqy/node_modules/esbuild/lib/main.js:1626:15)\r\n at eval (file:///home/projects/github-voetqy/node_modules/esbuild/lib/main.js:827:29)\r\n at responseCallbacks.\u003Ccomputed> (file:///home/projects/github-voetqy/node_modules/esbuild/lib/main.js:687:9)\r\n at handleIncomingPacket (file:///home/projects/github-voetqy/node_modules/esbuild/lib/main.js:742:9)\r\n at Socket.readFromStdout (file:///home/projects/github-voetqy/node_modules/esbuild/lib/main.js:663:7)\r\n at EventEmitter.emit (https://githubvoetqy-0f5x.w-corp.staticblitz.com/blitz.c8358679.js:35:156830)\r\n at S.emit (https://githubvoetqy-0f5x.w-corp.staticblitz.com/blitz.c8358679.js:35:1539231)\r\n at addChunk (https://githubvoetqy-0f5x.w-corp.staticblitz.com/blitz.c8358679.js:35:727409)\r\n at readableAddChunk (https://githubvoetqy-0f5x.w-corp.staticblitz.com/blitz.c8358679.js:35:727113)\r\n at Readable.push (https://githubvoetqy-0f5x.w-corp.staticblitz.com/blitz.c8358679.js:35:727797\r\nClick outside or fix the code to dismiss.\r\nYou can also disable this overlay by setting server.hmr.overlay to false in vite.config.js.\n```\n",[2937,2938],{"name":2908,"color":2909},{"name":2897,"color":2898},20369,"Passing a seemingly empty type to defineProps with defineDefaults throws an error","2023-04-18T18:03:39Z","https://github.com/nuxt/nuxt/issues/20369",0.6831228,{"description":2945,"labels":2946,"number":2951,"owner":2869,"repository":2869,"state":2917,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.1\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: pnpm@9.1.4\r\n- Builder: -\r\n- User Config: ssr, future, components, css, typescript, modules, devtools, eslint, image, i18n, veeValidate\r\n- Runtime Modules: nuxt-icon@0.6.10, @nuxt/eslint@0.3.13, @nuxt/image@1.7.0, @nuxtjs/i18n@8.3.1, @pinia/nuxt@0.5.1, @vee-validate/nuxt@4.12.7\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-69djhq?file=app%2Fapp.vue\n\n### Describe the bug\n\nIf you check out the reproduction and run `nuxt typecheck` you'll see that\r\n```ts\r\nconst { data } = useFetch(\"/api/foo\")\r\nconst foo: string | undefined = data.value\r\n```\r\nreturns an error because the type of `data` still is `unknown | null` instead of corresponding to v4's new `undefined` return type\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2947,2948,2949,2950],{"name":2882,"color":2883},{"name":2908,"color":2909},{"name":2860,"color":2861},{"name":2866,"color":2867},27565,"useAsyncData's return type for data and error still is `| null` in v4","2024-06-12T16:32:54Z","https://github.com/nuxt/nuxt/issues/27565",0.68316126,{"description":2957,"labels":2958,"number":2963,"owner":2869,"repository":2964,"state":2917,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/epic-smoke-95wysw?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nUsing the `@update:model-value` event handler produces type errors with the Select component, starting from nuxt-ui v3.1.0 (v3.0.2 works fine).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nType 'boolean | AcceptableValue | undefined' is not assignable to type '\"yes\" | \"no\"'.\n Type 'undefined' is not assignable to type '\"yes\" | \"no\"'.ts-plugin(2322)\n```",[2959,2960],{"name":2860,"color":2861},{"name":2961,"color":2962},"v3","49DCB8",4019,"ui","Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.6858669,{"description":2970,"labels":2971,"number":2979,"owner":2869,"repository":2869,"state":2917,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nThe official template shows this problem out of the box:\r\n\r\n```bash\r\nnpx nuxi init -t my-module\r\ncd my-module\r\nnpm i\r\n```\n\n### Describe the bug\n\nIn the `nuxt.config.ts` you should find this typing error:\r\n\r\n```\r\nType 'NuxtModule\u003CModuleOptions>' is not assignable to type 'string | NuxtModule\u003CModuleOptions> | [(string | NuxtModule\u003CModuleOptions> | undefined)?, ({ [x: string]: any; } | undefined)?] | undefined'.\r\n```\r\n\r\nAdditionally, the types seem to be too loose and not autocomplete:\r\n\r\n```ts\r\nimport MyModule from '..'\r\n\r\nexport default defineNuxtConfig({\r\n modules: [\r\n [MyModule, {\r\n // no autocompletion here\r\n }]\r\n ],\r\n myModule: {\r\n // or here\r\n addPlugin: true\r\n }\r\n})\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2972,2973,2974,2975,2976],{"name":2882,"color":2883},{"name":2908,"color":2909},{"name":2885,"color":2886},{"name":2860,"color":2861},{"name":2977,"color":2978},"schema","1d76db",15750,"Invalid types for `ModuleOptions` in `NuxtModule`","2023-01-22T00:09:19Z","https://github.com/nuxt/nuxt/issues/15750",0.6869759,{"description":2985,"labels":2986,"number":2991,"owner":2869,"repository":2869,"state":2917,"title":2992,"updated_at":2993,"url":2994,"score":2995},"### Versions\r\n\r\n- nuxt: 2.15.3\r\n- node: v14.16.0\r\n\r\n### Reproduction\r\n\r\nI set up a fresh installation of Nuxt today for a project. I use the above mentioned version with Typescript.\r\n\r\nThen I created the component below and created a constant there in the data() method using a constant declaration and also assigned a type to it, as well as returned it via the return object. \r\n\r\nWhen running `npm run dev` I got the following error message, which I can't understand. Because I wrote the same thing in another project with an older Nuxt version and it could be executed.\r\n\r\n```bash\r\n✔ Builder initialized 21:42:22\r\n✔ Nuxt files generated 21:42:22\r\n\r\n✖ Client\r\n Compiled with some errors in 5.93s\r\n\r\n\r\n ERROR Failed to compile with 1 errors friendly-errors 21:42:29\r\n\r\n\r\n ERROR in ./components/form.vue?vue&type=script&lang=ts& friendly-errors 21:42:29\r\n\r\nModule parse failed: Unexpected token (29:17) friendly-errors 21:42:29\r\nFile was processed with these loaders:\r\n * ./node_modules/vue-loader/lib/index.js\r\nYou may need an additional loader to handle the result of these loaders.\r\n| export default Vue.extend({\r\n| data() {\r\n> const taxable: Taxable | null = null\r\n| \r\n| return {\r\n friendly-errors 21:42:29\r\n @ ./components/form.vue?vue&type=script&lang=ts& 1:0-116 1:132-135 1:137-250 1:137-250\r\n @ ./components/form.vue\r\n @ ./.nuxt/components/plugin.js\r\n @ ./.nuxt/index.js\r\n @ ./.nuxt/client.js\r\n @ multi ./node_modules/eventsource-polyfill/dist/browserify-eventsource.js (webpack)-hot-middleware/client.js?reload=true&timeout=30000&ansiColors=&overlayStyles=&path=%2F__webpack_hmr%2Fclient&name=client ./.nuxt/client.js\r\n friendly-errors 21:42:29\r\nℹ Waiting for file changes 21:42:29\r\nℹ Memory usage: 201 MB (RSS: 317 MB) 21:42:29\r\nℹ Listening on: http://localhost:3000/ 21:42:29\r\n```\r\n\r\n\r\n### Steps to reproduce\r\nI have created this SFC.\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Csection class=\"relative w-full h-auto py-8\">\r\n \u003C!-- some html stuff - not interested! -->\r\n \u003C/section>\r\n\u003C/template>\r\n\r\n\u003Cscript lang=\"ts\">\r\nimport Vue from 'vue'\r\nimport { Taxable } from '~/interfaces/index' // return a valid typescript interface\r\n\r\nexport default Vue.extend({\r\n data() {\r\n const taxable: Taxable | null = null\r\n\r\n return {\r\n taxable,\r\n }\r\n }\r\n})\r\n\u003C/script>\r\n\r\n\u003Cstyle lang=\"scss\">\r\n// some styling\r\n\u003C/style>\r\n```\r\n\r\n### What is Expected?\r\nI expect this to compile correctly and launch the app.\r\n\r\n### What is actually happening?\r\nBuild aborts.",[2987,2988],{"name":2897,"color":2898},{"name":2989,"color":2990},"2.x","d4c5f9",9047,"Nuxt build aborts on const declaration in data() - Typescript","2023-01-22T15:38:48Z","https://github.com/nuxt/nuxt/issues/9047",0.6874383,["Reactive",2997],{},["Set"],["ShallowReactive",3000],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fY_QNdBemv5L1P4ybZkoFRpTHhTapZEoHWnDzA-T9DDY":-1},"/nuxt/ui/2043"]