\n \u003CNuxtWelcome />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconsole.log(\"111\");\n\u003C/script>\n```\n\n### Expected Behavior\nBuilt-in components should be auto-imported without errors during development.\n\n### Actual Behavior\nConsole errors occur for built-in components (e.g., `NuxtWelcome`), and auto-importing fails.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nWARN [Vue warn]: Failed to resolve component: NuxtRouteAnnouncer\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CApp> \n at \u003CNuxtRoot>\n\nthis is setup\n```",[3075],{"name":3076,"color":3077},"🔨 p3-minor","FBCA04",32290,"[Bug] AutoImport Fails for Components with `vite.esbuild.minifyWhitespace=true` in Dev Mode","2025-06-06T04:42:30Z","https://github.com/nuxt/nuxt/issues/32290",0.67175907,{"description":3084,"labels":3085,"number":3093,"owner":3026,"repository":3026,"state":3027,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Environment\n\nRootDir: /Users/dev02/dev/temporario/app-nuxt-3\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.10`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `app`, `css`, `windicss`, `build`, `modules`, `experimental`, `components`, `vite`, `runtimeConfig`, `intlify`, `vueuse`, `content`\r\n- Runtime Modules: `@intlify/nuxt3@0.2.4`, `@pinia/nuxt@0.4.6`, `@nuxt/content@2.2.2`, `@vueuse/nuxt@9.6.0`, `nuxt-windicss@2.5.5`, `nuxt-icon@0.1.8`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\n// app-nuxt-3/test/hoje.test.js\r\n\r\nimport { fileURLToPath } from 'node:url'\r\nimport { describe, expect, it } from 'vitest'\r\nimport { isWindows } from 'std-env'\r\nimport { setup, fetch, $fetch, startServer, createPage, url } from '@nuxt/test-utils'\r\n\r\nawait setup({\r\n rootDir: fileURLToPath(new URL('../../app-nuxt-3', import.meta.url)),\r\n server: true,\r\n browser: false,\r\n setupTimeout: (isWindows ? 240 : 120) * 1000\r\n})\r\n\r\ndescribe('pages', () => {\r\n it('render index', async () => {\r\n const html = await $fetch('/')\r\n expect(html).toContain('Fundação de Esportes DEV')\r\n })\r\n\r\n\r\n\n\n### Describe the bug\n\nHere are the links to the documentation and the example I took to make mine.\r\nhttps://nuxt.com/docs/getting-started/testing\r\nhttps://github.com/nuxt/framework/tree/main/test\r\n\r\nThe issue I'm having is the app is telling me the Url must be from the schema file. I'm in doubt if the Url is wrong when pointing to the application or if the scheme he wants to say is something else. I can't find any examples on the internet that help me.\r\nNote: Remembering that I configured Vitest and use it normally, including together with Pinia. The real problem is when I started testing the Nuxt components themselves. I haven't even started yet.\r\n\r\nError picture:\r\n\r\n\u003Cimg width=\"643\" alt=\"Captura de Tela 2023-01-09 às 10 42 12\" src=\"https://user-images.githubusercontent.com/83841469/211322216-b68c08fa-1f02-4793-9a03-bd8e275439c1.png\">\r\n\n\n### Additional context\n\nIt's my first time writing a bug (I've always been able to solve it by searching), so forgive me if it's not good enough.\n\n### Logs\n\n_No response_",[3086,3089,3090],{"name":3087,"color":3088},"3.x","29bc7f",{"name":3036,"color":3077},{"name":3091,"color":3092},"⛔️ can be closed","484893",12368,"Problem starting @nuxt/test-utils with URL","2023-02-07T07:10:45Z","https://github.com/nuxt/nuxt/issues/12368",0.6768507,{"description":3099,"labels":3100,"number":3101,"owner":3026,"repository":3044,"state":3027,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Environment\r\n\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.8`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `modules`\r\n- Runtime Modules: `vite-plugin-vue-type-imports/nuxt`\r\n- Build Modules: `-`\r\n\r\n### Reproduction\r\n\r\n#### How to recreate\r\n\r\nFor every link:\r\n\r\n1. Open a link.\r\n2. Wait for a development server is start and the Nuxt Welcome page is loaded.\r\n4. Press \u003Ckbd>Ctrl\u003C/kbd> + \u003Ckbd>C\u003C/kbd> in Terminal.\r\n5. Run `npm test`.\r\n\r\n#### Broken\r\n\r\nhttps://stackblitz.com/edit/github-owtwqh-82agcd?file=nuxt.config.ts,modules%2Fvite-plugin-vue-type-imports.ts,app.vue\r\n\r\n##### Load a bundled Nuxt module from the `node_modules` directory\r\n\r\n```ts\r\nexport default defineNuxtConfig({\r\n modules: [\r\n 'vite-plugin-vue-type-imports/nuxt',\r\n ],\r\n});\r\n```\r\n\r\n#### Working\r\n\r\nhttps://stackblitz.com/edit/github-owtwqh-dyj8f8?file=nuxt.config.ts,modules%2Fvite-plugin-vue-type-imports.ts,app.vue\r\n\r\n##### Load a local Nuxt module from the `modules/` directory\r\n\r\n```ts\r\nexport default defineNuxtConfig({\r\n modules: [\r\n '~/modules/vite-plugin-vue-type-imports.ts',\r\n ],\r\n});\r\n```\r\n\r\n### Describe the bug\r\n\r\nThe `vite-plugin-vue-type-imports/nuxt` module added in `nuxt.config.ts` is:\r\n\r\n* works when loaded via `npm run dev`;\r\n* broken if loaded via `npm test` (`nuxt test` or `vitest` with `@nuxt/test-utils-edge`).\r\n\r\n### Additional context\r\n\r\nThe [same Nuxt module code](https://github.com/wheatjs/vite-plugin-vue-type-imports/blob/370fcea9c7a09a0961bdf6e29b0795963034eb1e/src/nuxt.ts) is works with `npm test` if copy-pasted and loaded as a local plugin from the `modules/` directory.\r\n\r\n### Logs\r\n\r\n```shell\r\nERROR TypeError: Invalid URL 22:18:50\r\n\r\n ❯ TypeError.get https:/github-owtwqh-82agcd.w.staticblitz.com/blitz.df64f655701fde45529fa8e152b3842072335b47.js:6:292488\r\n 22:18:50\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nSerialized Error: { 22:18:50\r\n \"code\": \"ERR_INVALID_URL\",\r\n \"input\": \"//\",\r\n}\r\n```\r\n",[],429,"Vitest with `@nuxt/test-utils-edge` breaks imported `vite-plugin-vue-type-imports/nuxt` module, but works if same module code is recreated locally","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/429",0.6769126,{"description":3107,"labels":3108,"number":3111,"owner":3026,"repository":3026,"state":3027,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Environment\n\nNot really relevant to this issue...\r\n\r\n```\r\nNuxi 3.5.0 08:55:25\r\n 08:55:25\r\nRootDir: /home/dolf/rsc/vv-public/experimental 08:55:25\r\nNuxt project info: 08:55:25\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.14.0\r\n- Nuxt Version: 3.5.0\r\n- Nitro Version: 2.4.1\r\n- Package Manager: yarn@3.5.1\r\n- Builder: vite\r\n- User Config: typescript, vite, runtimeConfig, appConfig, css, sourcemap, modules, vuetify, i18n, piniaPersistedstate\r\n- Runtime Modules: @invictus.codes/nuxt-vuetify@0.2.20, @nuxtjs/i18n@8.0.0-beta.12, @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.1.1\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nThis is just a Typescript API mismatch, not really a runtime bug, so I don't think a reproduction is relevant. Just compare these lines:\r\n\r\nhttps://github.com/nuxt/nuxt/blob/a672cd7a4291eb812d76b9841ec516cd8609c680/packages/nuxt/src/app/nuxt.ts#L141\r\n\r\nhttps://github.com/vuejs/core/blob/020851e57d9a9f727c6ea07e9c1575430af02b73/packages/runtime-core/src/apiInject.ts#L9\r\n\r\n\n\n### Describe the bug\n\nIt should be possible to use `provide` with `Symbol`s, not just `string`s.\n\n### Additional context\n\nSee the Vue docs at https://vuejs.org/api/application.html#app-provide \n\n### Logs\n\n_No response_",[3109,3110],{"name":3087,"color":3088},{"name":3020,"color":3021},21022,"`nuxtApp.provide()` accepts `string` but not `symbol` or `InjectionKey\u003CT>`","2023-05-23T10:34:30Z","https://github.com/nuxt/nuxt/issues/21022",0.6770555,{"description":3117,"labels":3118,"number":3122,"owner":3026,"repository":3044,"state":3027,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.11.0\n- Nuxt Version: -\n- CLI Version: 3.25.1\n- Nitro Version: -\n- Package Manager: npm@11.1.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\n`pnpm create nuxt my-nuxt-project` and select all options\n\n### Describe the bug\n\n ERROR Error while importing module @nuxt/test-utils: Error: Cannot find module 'vitest/config' 9:37:22 AM\nRequire stack:\n- my-nuxt-project/node_modules/.pnpm/@nuxt+test-utils@3.19.0_@types+node@22.15.19_jiti@2.4.2_lightningcss@1.30.1_magicast@0.3.5_te_3u24m677fvme6kharjp6d5jt74/node_modules/@nuxt/test-utils/dist/config.mjs\n\n at loadNuxtModuleInstance (my-nuxt-project/node_modules/.pnpm/@nuxt+kit@3.17.3_magicast@0.3.5/node_modules/@nuxt/kit/dist/index.mjs:2571:15)\n at async installModule (my-nuxt-project/node_modules/.pnpm/@nuxt+kit@3.17.3_magicast@0.3.5/node_modules/@nuxt/kit/dist/index.mjs:2486:67)\n at async initNuxt (my-nuxt-project/node_modules/.pnpm/nuxt@3.17.3_@parcel+watcher@2.5.1_@types+node@22.15.19_better-sqlite3@11.10.0_db0@0.3.2_\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3119],{"name":3120,"color":3121},"good first issue","7057ff",1303,"Adding nuxt/test-utils errors without vitest","2025-05-23T04:45:47Z","https://github.com/nuxt/test-utils/issues/1303",0.6778469,{"labels":3128,"number":3132,"owner":3026,"repository":3026,"state":3027,"title":3133,"updated_at":3134,"url":3135,"score":3136},[3129,3130,3131],{"name":3087,"color":3088},{"name":3020,"color":3021},{"name":3036,"color":3077},14571,"Error: [nuxt] [request error] Context is not available","2023-01-19T17:37:15Z","https://github.com/nuxt/nuxt/issues/14571",0.67856663,{"description":3138,"labels":3139,"number":3141,"owner":3026,"repository":3044,"state":3027,"title":3142,"updated_at":3143,"url":3144,"score":3145},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.17.1\n- Nuxt Version: 4.0.2\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: compatibilityDate, app, components, css, debug, devtools, logLevel, modules, runtimeConfig, typescript, eslint, ssr, spaLoadingTemplate, vite, imports, build, experimental, hooks, telemetry\n- Runtime Modules: @nuxt/devtools@2.6.2, @nuxt/eslint@1.7.1, @pinia/nuxt@0.11.2, @nuxt/test-utils/module@3.19.2\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\n-\n\n### Describe the bug\n\nRunning tests in a Nuxt 4 environment using `renderSuspended()` errors due to missing reference in dist/build fro vue `getCurrentInstance()`.\n\nSymptoms:\n```\nReferenceError: getCurrentInstance is not defined\n ❯ interceptEmitOnCurrentInstance ../node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:285:29\n ❯ wrappedSetup ../node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:297:5\n ❯ setup ../node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:396:44\n ❯ callWithErrorHandling ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:200:19\n ❯ setupStatefulComponent ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7910:25\n ❯ setupComponent ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:7871:36\n ❯ mountComponent ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5188:7\n ❯ processComponent ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5154:9\n ❯ patch ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4681:11\n ❯ ReactiveEffect.componentUpdateFn [as fn] ../node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5300:11\n```\n\n\nBuild output `distribution/runtime-utils/index.mjs`\n```\nimport { reactive, h as h$1, Suspense, nextTick, unref, isReadonly, getCurrentInstance as getCurrentInstance$1, defineComponent as defineComponent$1, effectScope } from 'vue';\n\n...\n\n\nasync function renderSuspended(component, options) {\n\n...\n\n function interceptEmitOnCurrentInstance() {\n const currentInstance = getCurrentInstance(); // \u003C==== getCurrentInstance not present in imports\n if (!currentInstance) {\n return;\n }\n currentInstance.emit = getInterceptedEmitFunction(currentInstance.emit);\n }\n\n...\n\n}\n```\n\n`getCurrentInstane()` is being called while not imported in `src/runtime-utils/render.ts`. However, `src/runtime-utils/mount.ts` does correctly import `getCurrentInstance()`, leading to `getCurrentInstance as getCurrentInstance$1` in the build output (which doesn't help this instance of using the function).\n\nAdding the import in render.ts fixes the issue.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3140],{"name":3020,"color":3039},1371,"runtime-utils build missing getCurrentInstance in renderSuspended()","2025-07-30T18:38:00Z","https://github.com/nuxt/test-utils/issues/1371",0.67882997,["Reactive",3147],{},["Set"],["ShallowReactive",3150],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkKpuwCilpu5-3V6pT5zNlQXVKOpMPwF3RUP_WskAM6Q":-1},"/nuxt/ui/4579"]