\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```",[2935],{"name":2936,"color":2898},"🔨 p3-minor",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.69400144,{"labels":2943,"number":2946,"owner":2875,"repository":2875,"state":2903,"title":2947,"updated_at":2948,"url":2949,"score":2950},[2944,2945],{"name":2886,"color":2887},{"name":2916,"color":2917},9136,"刷新页面时使用fetch调用接口发现vuex存的内容没有重置为初始值","2023-01-22T15:44:51Z","https://github.com/nuxt/nuxt/issues/9136",0.6943673,{"labels":2952,"number":2955,"owner":2875,"repository":2875,"state":2903,"title":2956,"updated_at":2948,"url":2957,"score":2958},[2953,2954],{"name":2886,"color":2887},{"name":2916,"color":2917},9106,"Cf","https://github.com/nuxt/nuxt/issues/9106",0.6997322,{"description":2960,"labels":2961,"number":2969,"owner":2875,"repository":2875,"state":2903,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### 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_",[2962,2965,2966],{"name":2963,"color":2964},"3.x","29bc7f",{"name":2869,"color":2898},{"name":2967,"color":2968},"⛔️ 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.7003745,{"description":2975,"labels":2976,"number":2979,"owner":2875,"repository":2875,"state":2903,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Describe the feature\n\nIt seems like irregardless of the parameters I pass into `setup` from `@nuxt/test-utils`, vitest always re-builds the entire app, even if nothing changed in it and the only change was in the test file.\r\n\r\nI can pre-build the app and disable the test build step using `build: false`, but even that wasn't trivial to configure (because it always tries to use its own randomly generated build folder) and it would be better to be able to re-build during testing just when it's actually needed not on every test run.\r\n\r\nFor anyone interested, this is what I had to get done to get the tests to run from the standard `.output` directory:\r\n\r\n```random.spec.ts\r\n// Basic nuxt e2e test with vitest\r\nimport { createPage, setup } from '@nuxt/test-utils'\r\nimport { describe, it, expect } from 'vitest'\r\nimport path from 'path'\r\n\r\nconst mainOutputDir = path.resolve(__dirname, '../../.output')\r\n\r\ndescribe('viewer', async () => {\r\n //\r\n await setup({\r\n buildDir: mainOutputDir,\r\n build: false,\r\n nuxtConfig: {\r\n buildDir: mainOutputDir,\r\n nitro: {\r\n output: {\r\n dir: mainOutputDir\r\n }\r\n }\r\n }\r\n })\r\n\r\n it('renders the viewer', async () => {\r\n const page = await createPage('/projects/9387e7e4c2/models/51c7c5b8eb')\r\n await page.waitForSelector('#speckle')\r\n const content = await page.content()\r\n expect(content).toMatch('helloworld')\r\n }, 100000)\r\n})\r\n\r\n```\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2977,2978],{"name":2963,"color":2964},{"name":2886,"color":2887},21906,"[@nuxt/test-utils] nuxt shouldn't rebuild from scratch every time a test re-runs","2023-12-02T00:18:11Z","https://github.com/nuxt/nuxt/issues/21906",0.70296544,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fX3PH4s71Tkyat4NkpvLYNU1owVZw8JCnw0SVw7E9W5U":-1},"/nuxt/ui/4302"]