\r\n \u003C/VTrigger>\r\n\u003C/template>\r\n```\r\n\r\n/components/v/Trigger/Trigger.tsx\r\n\r\n```\r\nimport {\r\n defineComponent,\r\n} from 'vue';\r\n\r\nexport default defineComponent({\r\n name: 'VTrigger',\r\n inheritAttrs: false,\r\n setup(props, { emit, slots, attrs }) {\r\n return () => {\r\n return (\r\n \u003C>\r\n \u003Cdiv>test\u003C/div>\r\n \u003C/>\r\n );\r\n };\r\n },\r\n});\r\n```\r\n\r\n\n\n### Describe the bug\n\n```\r\n[Vue Router warn]: uncaught error during route navigation: 14:39:42 \r\n[[vite-node] [ERR_MODULE_NOT_FOUND] /__vue-jsx-ssr-register-helper 14:39:42 \r\nat /__vue-jsx-ssr-register-helper (imported from E:/01.web/client/components/v/Trigger/Trigger.tsx)] {\r\n statusCode: 500,\r\n fatal: false,\r\n unhandled: false,\r\n statusMessage: 'Vite Error',\r\n __nuxt_error: true\r\n}\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3049,3052],{"name":3050,"color":3051},"3.x","29bc7f",{"name":3021,"color":3022},15698,"Can't use TSX component","2023-01-19T18:20:10Z","https://github.com/nuxt/nuxt/issues/15698",0.6173325,{"labels":3059,"number":3066,"owner":3024,"repository":3024,"state":3041,"title":3067,"updated_at":3068,"url":3069,"score":3070},[3060,3061,3062,3063],{"name":3050,"color":3051},{"name":3021,"color":3022},{"name":3035,"color":3036},{"name":3064,"color":3065},"layers","006B75",25230,"Wrong tsconfig when operating in monorepo","2024-05-24T14:00:23Z","https://github.com/nuxt/nuxt/issues/25230",0.63136536,{"description":3072,"labels":3073,"number":3082,"owner":3024,"repository":3024,"state":3041,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Windows 10 Home 10.0.19044 Build 19044`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.3.2`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `pnpm@7.30.3`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nNone\r\n\r\n### Describe the bug\r\n\r\nA fresh Nuxt app, nothing would complete on the config, only `modules` and `telemetry`.\r\n\r\nI thought this was a Nuxt related issue, so before I opened an issue, I tried to diagnose myself and filter out all I could:\r\n\r\nChanging nuxt version from 3.3.2 to 3.3.1, deleting .nuxt, deleting node_modules, reloading VSCode, restarting TS language server, changing Node version, etc.\r\n\r\nUntil I had an idea and checked VSCode installed TS version, and yup, that was it.\r\nMy latest VSCode version is using TS v4.8.4. \r\n\r\nSo I had to create the `.vscode/settings.json` (I rarely have to do this), and set a TS version for the workspace, forcing it to use v5.0.2, and just like that the config props appeared again.\r\n\r\nUntil now, all the Nuxt 3 apps I've made have been working beautifully (only 2 times where there were reported bugs and were fixed later).\r\n\r\nAny kind information will be appreciated.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3074,3077,3078,3081],{"name":3075,"color":3076},"types","2875C3",{"name":3050,"color":3051},{"name":3079,"color":3080},"workaround available","11376d",{"name":3021,"color":3022},19921,"Nuxt config types failing on VSCode installed typescript version","2023-04-29T05:40:05Z","https://github.com/nuxt/nuxt/issues/19921",0.638855,{"description":3088,"labels":3089,"number":3098,"owner":3024,"repository":3024,"state":3041,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.5.3\r\n- Nitro Version: 2.4.1\r\n- Package Manager: pnpm@8.6.1\r\n- Builder: vite\r\n- User Config: devtools, modules, css, eslint\r\n- Runtime Modules: @vueuse/nuxt@10.1.2, @nuxtjs/supabase@0.3.6, @nuxtjs/tailwindcss@6.7.0, @nuxtjs/eslint-module@4.1.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nYou can check a minimal reproduction in this repository: https://github.com/mitjans/nuxt-server-types\r\n\r\nTypescript complains that it cannot find the module `\"~/types/database\"`.\r\n\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nIt seems that with the new tsconfig file introduced in version 3.5.2, global nuxt import aliases do not work inside the server folder. Autocompletion suggests importing relative paths.\r\n\r\nAlso, other Nuxt modules imports stopped working. See [@nuxtjs/supabase issue 191](https://github.com/nuxt-modules/supabase/issues/191).",[3090,3091,3092,3095],{"name":3075,"color":3076},{"name":3050,"color":3051},{"name":3093,"color":3094},"dx","C39D69",{"name":3096,"color":3097},"upstream","E8A36D",21484,"Server tsconfig import aliases","2023-06-22T10:49:17Z","https://github.com/nuxt/nuxt/issues/21484",0.63938797,{"description":3104,"labels":3105,"number":3108,"owner":3024,"repository":3024,"state":3041,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v20.9.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.11.0\r\n- Builder: -\r\n- User Config: devtools, typescript, imports, components\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-ydvwun?file=app.vue\r\n\r\nThe error does not show immediately when the application starts. \r\nEdit the HTML of `app.vue` and save. The error is then shown\r\n\r\n### Describe the bug\r\n\r\nWhen using `\"allowJs\": false` in `tsconfig.json` and `typeCheck: true` is `nuxt.config.ts`, the following error is thrown by `vue-tsc` after an `hmr update` by editing a file:\r\n```\r\n ERROR(vue-tsc) File '/home/david/projects/no-js-error/node_modules/.pnpm/@nuxt+ui-templates@1.3.1/node_modules/@nuxt/ui-templates/dist/templates/welcome.vue.js' is a JavaScript file. Did you mean to enable the 'allowJs' option?\r\n The file is in the program because:\r\n Root file specified for compilation\r\n FILE undefined:\r\n\r\nundefined\r\n```\r\n\r\nThe `NuxtWelcome` component is not used in `app.vue`, but is included in `.nuxt/components.d.ts` along with many other unused components.\r\n\r\nI assumed, at the very least, the bundled components should be typescript components, or, preferably (and what I expected), unused components should not be bundled\r\n\r\n### Additional context\r\n\r\nTested with `npm` and `pnpm` and the same behavior is observed in both cases\r\n\r\n### Logs\r\n\r\n```shell-script\r\ndavid@david-desktop:~/projects/no-js-error$ pnpm run dev\r\n\r\n> nuxt-app@ dev /home/david/projects/no-js-error\r\n> nuxt dev\r\n\r\nNuxt 3.8.2 with Nitro 2.8.1 11:46:35\r\n 11:46:35\r\n ➜ Local: http://localhost:3000/\r\n ➜ Network: use --host to expose\r\n\r\n ➜ DevTools: press Shift + Alt + D in the browser (v1.0.5) 11:46:36\r\n\r\nℹ Vite server warmed up in 1125ms 11:46:37\r\nℹ Vite client warmed up in 1338ms 11:46:37\r\n✔ Nitro built in 390 ms nitro 11:46:38\r\n\r\n ERROR 11:46:38\r\n[vue-tsc] Found 0 errors. Watching for file changes.\r\n\r\nℹ hmr update /app.vue\r\n\r\n ERROR 11:46:45\r\n ERROR(vue-tsc) File '/home/david/projects/no-js-error/node_modules/.pnpm/@nuxt+ui-templates@1.3.1/node_modules/@nuxt/ui-templates/dist/templates/welcome.vue.js' is a JavaScript file. Did you mean to enable the 'allowJs' option?\r\n The file is in the program because:\r\n Root file specified for compilation\r\n FILE undefined:\r\n\r\nundefined\r\n\r\n[vue-tsc] Found 1 error. Watching for file changes.\r\n```\r\n",[3106,3107],{"name":3075,"color":3076},{"name":3021,"color":3022},24651,"Cannot use typescript typeCheck and allowJs: false simultaneously. vue-tsc error thrown","2025-05-30T11:26:47Z","https://github.com/nuxt/nuxt/issues/24651",0.6425394,{"description":3114,"labels":3115,"number":3118,"owner":3024,"repository":3024,"state":3041,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.17.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@9.6.6\r\n- Builder: -\r\n- User Config: devtools, typescript, vue, modules, i18n, quasar, site, nitro, routeRules, sitemap, runtimeConfig, css, security\r\n- Runtime Modules: @nuxtjs/i18n@8.3.1, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxtjs/seo@2.0.0-rc.10, nuxt-quasar-ui@2.1.2, nuxt-security@2.0.0-rc.9\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nit looks like auto import is not working\r\n\r\n\r\n### Describe the bug\r\n\r\nif i upgrade vue-tsc version,\r\n\r\ni can't npm run build or dev\r\n\r\nbecause I encounter errors with composable... etc.\r\n\r\n\r\n\r\n\r\n`components/recruit/Table.vue:29:11 - error TS2339: Property 'convertUnixtoYMD' does not exist on type 'CreateComponentPublicInstance\u003CReadonly\u003CExtractPropTypes\u003C__VLS_TypePropsToOption\u003C{ searchStr: string; data: RecruitList[]; }>>>, {}, unknown, ... 16 more ..., {}>'.\r\n\r\n29 convertUnixtoYMD(item.endTime)\r\n ~~~~~~~~~~~~~~~~\r\n`\r\n`components/solution/Intro.vue:40:21 - error TS2339: Property 'navigateTo' does not exist on type 'CreateComponentPublicInstance\u003CReadonly\u003CExtractPropTypes\u003C__VLS_TypePropsToOption\u003C{ data: Res_Solution; }>>>, { t: ComposerTranslation\u003C{ [x: string]: LocaleMessage\u003CVueMessageType>; }, ... 4 more ..., string>; }, ... 17 more ..., {}>'.\r\n\r\n40 @click=\"navigateTo({ path: '/customer/brochure' })\"\r\n ~~~~~~~~~~\r\n`\r\n\r\nit looks like auto import is not working\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_",[3116,3117],{"name":3021,"color":3022},{"name":3035,"color":3036},28440,"error with vue-tsc 2.0.29","2024-08-09T14:28:00Z","https://github.com/nuxt/nuxt/issues/28440",0.6427298,{"description":3124,"labels":3125,"number":3127,"owner":3024,"repository":3024,"state":3041,"title":3128,"updated_at":3129,"url":3130,"score":3131},"------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.18.3\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@11.1.0\n- Builder: -\n- User Config: components, css, devtools, modules, vite\n- Runtime Modules: @nuxt/fonts@0.10.3, @nuxt/icon@1.10.3, @vueuse/nuxt@12.7.0\n- Build Modules: -\n------------------------------\n\nI have 2 projects:\n\n```\nnuxt-projects/\n\tapp/\n\tui/\n```\n\nThere is package.json in each project and I did npm install.\n\nIn **app** project, I want to extends **ui**\n\n_ui nuxt.config.ts_\n```typescript\nimport tailwindcss from \"@tailwindcss/vite\";\n\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n // compatibilityDate: '2024-11-01',\n components: [\n {\n path: '~/components',\n pathPrefix: false,\n global: true, // useless for important components\n },\n ],\n css: [\"~/assets/css/main.css\"],\n devtools: { enabled: true },\n modules: [\n \"@nuxt/fonts\",\n \"@nuxt/icon\",\n \"@vueuse/nuxt\",\n ], \n vite: {\n plugins: [\n tailwindcss(),\n ],\n },\n})\n```\n\n_app nuxt.config.ts_\n\n```typescript\nimport tailwindcss from \"@tailwindcss/vite\";\n\n// https://nuxt.com/docs/api/configuration/nuxt-config\nexport default defineNuxtConfig({\n // compatibilityDate: '2024-11-01',\n components: [\n {\n path: '../ui/components', // required for import components\n pathPrefix: false,\n },\n {\n path: '~/components',\n pathPrefix: false,\n },\n ],\n\n css: [\"~/assets/css/main.css\"],\n devtools: { enabled: true },\n extends: [\"../ui\"], // useless for import components\n modules: [\n \"@nuxt/fonts\",\n \"@nuxt/icon\",\n \"@nuxt/content\",\n \"@vueuse/nuxt\",\n ],\n\n vite: {\n plugins: [\n tailwindcss(),\n ],\n },\n\n compatibilityDate: \"2025-03-05\",\n})\n```\n\nIf I add only \n\n```typescript\nextends: [\"../ui\"], \n```\n\nextends doesn't work. Ui componenets are not imported. \n\nIf I add \n\n```typescript\ncomponents: [\n {\n path: '../ui/components',\n pathPrefix: false,\n },\n```\n\nIt works but then extends is useless.\n\nCould you explain how to make works extends ?\nThere is a lack of documentation about extends.\n\n\n",[3126],{"name":3021,"color":3022},31221,"Question / Issue with nuxt extends for import components","2025-03-07T21:44:41Z","https://github.com/nuxt/nuxt/issues/31221",0.64444274,{"description":3133,"labels":3134,"number":3137,"owner":3024,"repository":3024,"state":3041,"title":3138,"updated_at":3139,"url":3140,"score":3141},"### Environment\n\n```console\r\n❯ npx nuxi info\r\nNuxi 3.4.1 3:15:16 PM\r\n 3:15:16 PM\r\nRootDir: /home/everyx/Projects/fengsi/ycymotors.com 3:15:16 PM\r\nNuxt project info: 3:15:16 PM\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.15.0\r\n- Nuxt Version: 3.4.1\r\n- Nitro Version: 2.3.3\r\n- Package Manager: pnpm@8.2.0\r\n- Builder: vite\r\n- User Config: typescript, telemetry, routeRules, runtimeConfig, app, css, modules, image, vite, experimental\r\n- Runtime Modules: @unocss/nuxt@0.51.4, @pinia/nuxt@0.4.8, @element-plus/nuxt@1.0.4, @nuxt/image-edge@1.0.0-28020728.5df24eb, nuxt-simple-sitemap@2.4.11\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new 3:15:16 PM\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\r\n```\n\n### Reproduction\n\nI want use a web component provide by [playerx](https://github.com/luwes/playerx), and setup vite config according to this article: [Using Custom Elements in Vue](https://vuejs.org/guide/extras/web-components.html#using-custom-elements-in-vue)\r\n\r\n```ts\r\nimport vue from '@vitejs/plugin-vue';\r\n\r\nexport default defineNuxtConfig({\r\n vite: {\r\n plugins: [\r\n vue({\r\n template: {\r\n compilerOptions: {\r\n isCustomElement: (tag) => [\r\n 'player-x',\r\n ].includes(tag),\r\n },\r\n },\r\n }),\r\n ],\r\n },\r\n});\r\n```\r\n\r\nThen use `npm run dev`, I got this error:\r\n\r\n```console\r\n 3:22:22 PM\r\n\r\n ERROR At least one \u003Ctemplate> or \u003Cscript> is required in a single file component. (x11) 3:22:22 PM\r\n\r\nℹ Vite client warmed up in 3718ms 3:22:23 PM\r\n✔ Nitro built in 1384 ms nitro 3:22:24 PM\r\n```\n\n### Describe the bug\n\nWhen I remove the vite plugin config, everything is back to get work, but I will see the vue wram:\r\n\r\n```console\r\n[Vue warn]: Failed to resolve component: player-x 3:26:27 PM\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n```\r\n\r\nI also check this issues before: https://github.com/nuxt/nuxt/issues/20228 , but it's not working for me, I can still see this wram.\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3135,3136],{"name":3050,"color":3051},{"name":3021,"color":3022},20384,"Can not set Custom Elements in Vite Config","2023-04-19T08:13:16Z","https://github.com/nuxt/nuxt/issues/20384",0.64720917,["Reactive",3143],{},["Set"],["ShallowReactive",3146],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fWZliRqVc7lKQ475-6t9VuN7-o34quXBWJcMeNlLnk70":-1},"/nuxt/nuxt/13443"]