\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nwithDefaults(\r\n defineProps\u003C{\r\n variant: \"fill\" | \"ghost\";\r\n }>(),\r\n { variant: \"fill\" }\r\n);\r\n\u003C/script>\r\n```\r\n\r\n`~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\ndeclare module 'vue' {\r\n export interface GlobalComponents {\r\n //...\r\n 'MyButton': typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n //...\r\n }\r\n}\r\n\r\nexport const MyButton: typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n\r\nexport const componentNames: string[]\r\n```\r\n\r\n\r\n### Correct Intellisense\r\n\r\nVsCode popopver hovering `'MyButton'` in `~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\n(property) GlobalComponents['MyButton']: __VLS_WithTemplateSlots\u003CDefineComponent\u003C{\r\n variant: {\r\n type: PropType\u003C\"fill\" | \"ghost\">;\r\n required: true;\r\n default: string;\r\n };\r\n}, {}, unknown, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, ... 5 more ..., {}>, {\r\n ...;\r\n}>\r\n````\r\n\r\n### Wrong Intellisense\r\n\r\nVsCode popopver hovering `\u003CMyButton />` in the template block of `~/app.vue` (or any other template)\r\n\r\n```TypeScript\r\n(property) 'MyButton': DefineComponent\u003C{}, {}, any>\r\n```\r\n\r\n### Additional context\r\n\r\nThe above example is the current state of the reproduction repo. But a different, but similar behavior happened in other reports (for example a yarn workspace repo). Strange enough, sometimes, it works fine...\r\n\r\n### Logs\r\n\r\n_No response_",[3087,3088,3089,3090],{"name":3057,"color":3058},{"name":3039,"color":3040},{"name":3020,"color":3021},{"name":3023,"color":3024},21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.6325201,{"labels":3097,"number":3106,"owner":3026,"repository":3026,"state":3048,"title":3107,"updated_at":3108,"url":3109,"score":3110},[3098,3099,3100,3103],{"name":3039,"color":3040},{"name":3042,"color":3043},{"name":3101,"color":3102},"components","05B979",{"name":3104,"color":3105},"❗ p4-important","D93F0B",13538,"Autoimport components dir","2023-10-06T09:49:35Z","https://github.com/nuxt/nuxt/issues/13538",0.6354687,{"description":3112,"labels":3113,"number":3122,"owner":3026,"repository":3026,"state":3048,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.15.1\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.27\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-hxerk6?file=app.tsx\n\n### Describe the bug\n\nComponents types are not being auto imported when working with `tsx` files instead `vue`. (But they render ok)\r\nFor example I get: `Cannot find name 'NuxtLink'.`\r\nBut if I import the `NuxtLink` from `#components` manually I get the typings.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3114,3115,3116,3119],{"name":3057,"color":3058},{"name":3042,"color":3043},{"name":3117,"color":3118},"🔨 p3-minor","FBCA04",{"name":3120,"color":3121},"✨ good reproduction","fbca04",28781,"(tsx) Auto imports typings","2024-09-02T11:02:48Z","https://github.com/nuxt/nuxt/issues/28781",0.6381755,{"labels":3128,"number":3131,"owner":3026,"repository":3026,"state":3048,"title":3132,"updated_at":3133,"url":3134,"score":3135},[3129,3130],{"name":3039,"color":3040},{"name":3042,"color":3043},12005,"nuxt3 does not export NuxtConfig","2023-01-19T16:03:31Z","https://github.com/nuxt/nuxt/issues/12005",0.63819385,{"description":3137,"labels":3138,"number":3143,"owner":3026,"repository":3026,"state":3048,"title":3144,"updated_at":3145,"url":3146,"score":3147},"### Environment\r\n\r\n- Operating System: `Linux`\r\n- Node Version: `v14.17.1`\r\n- Nuxt Version: `3-3.0.0-27234211.2a0afbd`\r\n- Package Manager: `Yarn`\r\n- Bundler: `Webpack`\r\n- User Config: `meta`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n### Describe the bug and expected behavior\r\n\r\nI am trying to globally import a stylesheet into nuxt.config.js:\r\n```\r\nimport { defineNuxtConfig } from 'nuxt3'\r\n\r\nexport default defineNuxtConfig({\r\n meta: {\r\n style: [\r\n '~/assets/scss/global.scss',\r\n ]\r\n }\r\n})\r\n```\r\n\r\nBut when launching the application, there are several errors in the console and terminal:\r\n```\r\nentry.mjs:39 Error while mounting app: DOMException: Failed to execute 'setAttribute' on 'Element': '0' is not a valid attribute name.\r\n at createElement (http://localhost:3000/_nuxt/node_modules/@vueuse/head/dist/index.mjs?v=8287862b:47:10)\r\n at insertTags (http://localhost:3000/_nuxt/node_modules/@vueuse/head/dist/index.mjs?v=8287862b:199:22)\r\n at Object.updateDOM (http://localhost:3000/_nuxt/node_modules/@vueuse/head/dist/index.mjs?v=8287862b:259:7)\r\n at http://localhost:3000/_nuxt/node_modules/nuxt3/dist/meta/runtime/lib/vueuse-head.plugin.mjs:14:12\r\n at callWithErrorHandling (http://localhost:3000/_nuxt/node_modules/.vite/vue.js?v=8287862b:6280:18)\r\n at callWithAsyncErrorHandling (http://localhost:3000/_nuxt/node_modules/.vite/vue.js?v=8287862b:6288:17)\r\n at ReactiveEffect.getter [as fn] (http://localhost:3000/_nuxt/node_modules/.vite/vue.js?v=8287862b:6564:16)\r\n at ReactiveEffect.run (http://localhost:3000/_nuxt/node_modules/.vite/vue.js?v=8287862b:391:21)\r\n at doWatch (http://localhost:3000/_nuxt/node_modules/.vite/vue.js?v=8287862b:6645:13)\r\n at watchEffect (http://localhost:3000/_nuxt/node_modules/.vite/vue.js?v=8287862b:6502:10)\r\n```\r\n\r\nAn incorrect file link appears in the \u003Chead> tag:\r\n`\u003Cstyle 0=\"~\" 1=\"/\" 2=\"a\" 3=\"s\" 4=\"s\" 5=\"e\" 6=\"t\" 7=\"s\" 8=\"/\" 9=\"s\" 10=\"c\" 11=\"s\" 12=\"s\" 13=\"/\" 14=\"g\" 15=\"l\" 16=\"o\" 17=\"b\" 18=\"a\" 19=\"l\" 20=\".\" 21=\"s\" 22=\"c\" 23=\"s\" 24=\"s\">\u003C/style>`\r\n\r\n### Steps to reproduce\r\nSteps to reproduce the behavior:\r\n1. Create file assets/scss/global.scss\r\n2. Go to nuxt.config.js\r\n3. Add follow code inside defineNuxtConfig function\r\n```\r\nmeta: {\r\n style: [\r\n '~/assets/scss/global.scss',\r\n ]\r\n }\r\n```\r\n4. run yarn dev\r\n5. Open localhost:3000 and see an error in console and wrong \u003Cscript> tag inside \u003Chead> tag",[3139,3140,3141],{"name":3039,"color":3040},{"name":3042,"color":3043},{"name":3142,"color":3118},"needs reproduction",11894,"Problem when importing global styles in nuxt.config","2023-01-19T15:58:32Z","https://github.com/nuxt/nuxt/issues/11894",0.6421097,["Reactive",3149],{},["Set"],["ShallowReactive",3152],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fO0cId0_DuFJim7MNe1EDcwRj6xvdf_CSv4pqkruFoD8":-1},"/nuxt/nuxt/12962"]