`. Works fine for `\u003Cscript/>`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3036,3039],{"name":3037,"color":3038},"3.x","29bc7f",{"name":3040,"color":3041},"🔨 p3-minor","FBCA04",15674,"closed","Runs `\u003Cscript setup/>` 2 times after starting `nuxt dev`","2023-01-21T23:56:10Z","https://github.com/nuxt/nuxt/issues/15674",0.6530165,{"description":3049,"labels":3050,"number":3055,"owner":3027,"repository":3027,"state":3043,"title":3056,"updated_at":3057,"url":3058,"score":3059},"### Environment\r\n\r\nNuxi 3.1.0 00:58:57\r\n 00:58:57\r\nRootDir: /workspace/tester-plugin-nuxt-config 00:58:57\r\nNuxt project info: 00:58:57\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v14.21.2`\r\n- Nuxt Version: `3.1.0`\r\n- Nitro Version: `2.0.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new 00:58:57\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\r\n### Reproduction\r\n\r\nWrite two Mocha tests. In the first, build Nuxt 3. In the second, do anything.\r\n\r\n### Describe the bug\r\n\r\nWhen building Nuxt 3 programmatically, all console output is wrapped. But this has side effects since also all outputs after the build is wrapped. Currently, when using Nuxt 3 programmatically in a Mocha test, the Mocha test cases aren't output.\r\n\r\nI think this is related to the `logger.restoreAll()` and `logger.wrapAll()` calls.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3051,3052,3053],{"name":3037,"color":3038},{"name":3018,"color":3019},{"name":3054,"color":3041},"needs reproduction",18498,"Nuxt 3 swallows log output after building","2023-02-22T11:26:02Z","https://github.com/nuxt/nuxt/issues/18498",0.66141385,{"description":3061,"labels":3062,"number":3064,"owner":3027,"repository":3027,"state":3043,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `pnpm@8.11.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `vite`, `nitro`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n\n### Reproduction\n\nI have prepared a minimal reproduction on [this repo](https://github.com/KUN1007/nuxt-317-console-log-error).\n\n1. Clone [this repo](https://github.com/KUN1007/nuxt-317-console-log-error)\n2. Run `pnpm i && pnpm dev`\n\nCurrent Behavior\nOpen the application in your browser and inspect the developer console. There is no text output to the console.\n\n\n\n\n\nExpected Behavior\nWhen running the application in development mode (`pnpm dev`), all console.log statements should be preserved and function as expected.\nFirst we comment the code on `nuxt.config.ts`\n```ts\n // vite: {\n // esbuild: {\n // drop: ['console'],\n // },\n // },\n\n // nitro: {\n // esbuild: {\n // options: {\n // drop: ['console'],\n // },\n // },\n // },\n```\nAnd re-run `pnpm dev`, open `http://localhost:3000/` in your browser.\n\n\n\n\n\nThe `vite.esbuild.drop` setting should only apply during a production build (`pnpm build`).\n\n### Describe the bug\n\nIn the latest version of Nuxt, configuring `vite.esbuild.drop: ['console']` in `nuxt.config.ts` causes `console.log` statements to be removed in the development environment (when running `pnpm dev`).\nThis behavior is unexpected. The esbuild.drop option is intended for production optimization to strip out debugging code from the final bundle. It should not affect the development server, as `console.log` is a critical tool for debugging during development. This prevents developers from inspecting values and control flow in the browser console, significantly hindering the development process.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3063],{"name":3018,"color":3019},32445,"Bug: `vite.esbuild.drop: ['console']` incorrectly removes console logs in development mode","2025-06-20T11:43:13Z","https://github.com/nuxt/nuxt/issues/32445",0.6643771,{"description":3070,"labels":3071,"number":3075,"owner":3027,"repository":3027,"state":3043,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Environment\r\n\r\n[12:28:21 PM] Nuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.11.1\r\n- CLI Version: 3.11.0\r\n- Nitro Version: 2.9.4\r\n- Package Manager: yarn@3.2.0\r\n- Builder: -\r\n- User Config: typescript, modules, runtimeConfig, alias, vite, app, routeRules, nitro, build, hooks, prometheus\r\n- Runtime Modules: @nuxt/devtools@0.2.5, @nuxtjs/tailwindcss@6.3.0, ~/lib/core/nuxt-modules/apollo/module.ts, @speckle/ui-components-nuxt@0.0.1, @artmizu/nuxt-prometheus@2.2.1\r\n- Build Modules: -\r\n------------------------------\r\n\r\n[12:28:21 PM] 👉 Report an issue: https://github.com/nuxt/nuxt/issues/new\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\r\n### Reproduction\r\n\r\nIssue is obvious from code\r\n\r\n### Describe the bug\r\n\r\nThe new server log streaming to client feature (https://github.com/nuxt/nuxt/pull/25936/files) has essentially made it so that all `console.*` methods are proxied through Consola on the frontend. But there's no way to configure the Consola instance meaning its using its defaults, including the default log level.\r\n\r\nWhat this means in practice is that all `console.debug` calls are essentially skipped, because the `debug` log level is too low for the default log level.\r\n\r\n### Additional context\r\n\r\nIntroduced by this feature in nuxt 3.11: https://github.com/nuxt/nuxt/pull/25936/files\r\n\r\n### Logs\r\n\r\n_No response_",[3072,3073,3074],{"name":3037,"color":3038},{"name":3018,"color":3019},{"name":3054,"color":3041},26369,"dev server logging prevents `console.debug` calls from showing in browser","2024-05-24T14:03:22Z","https://github.com/nuxt/nuxt/issues/26369",0.67138696,{"labels":3081,"number":3089,"owner":3027,"repository":3027,"state":3043,"title":3090,"updated_at":3091,"url":3092,"score":3093},[3082,3085,3086],{"name":3083,"color":3084},"enhancement","8DEF37",{"name":3037,"color":3038},{"name":3087,"color":3088},"bug","d73a4a",14159,"implement `setupTimeout` option in test-utils","2023-01-19T17:26:34Z","https://github.com/nuxt/nuxt/issues/14159",0.68040085,{"description":3095,"labels":3096,"number":3102,"owner":3027,"repository":3103,"state":3043,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Environment\n\n- Operating System: Darwin\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: pnpm@9.6.0\n- Builder: -\n- User Config: modules, compatibilityDate\n- Runtime Modules: @nuxt/content@3.5.1\n- Build Modules: -\n\n### Reproduction\n\nI extended the Nuxt Content tests within the repo on my branch https://github.com/JessicaSachs/test-utils/pull/new/jess/vitest-nuxt-content\n\n### Describe the bug\n\n- Whenever `useRuntimeConfig` is used within the setup function of a component, the component fails to render. This happens for all the default Nuxt Content ProseH1-ProseH3 components.\n- Using `mountSuspended` within Vitest Browser Mode fails\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3097,3099],{"name":3083,"color":3098},"a2eeef",{"name":3100,"color":3101},"good first issue","7057ff",1283,"test-utils","support nuxt environment in browser mode","2025-05-15T13:23:03Z","https://github.com/nuxt/test-utils/issues/1283",0.6828661,{"description":3109,"labels":3110,"number":3114,"owner":3027,"repository":3027,"state":3043,"title":3115,"updated_at":3116,"url":3117,"score":3118},"### Environment\n\n```\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0-rc.11`\r\n- Nitro Version: `0.5.4`\r\n- Package Manager: `yarn@1.22.11`\r\n- Builder: `vite`\r\n```\r\n\r\nThough I have also tested with rc 10, 8, 5, & 4\n\n### Reproduction\n\nThis is fairly short so ill avoid reproduction unless theres a strong need\r\n\r\nFrom a fresh Nuxt 3 Project:\r\n\r\n```json\r\n// package.json\r\n\r\n{\r\n \"scripts\": {\r\n ...\r\n \"build\": \"nuxt build\",\r\n \"test\": \"vitest run\"\r\n },\r\n \"devDependencies\": {\r\n \"nuxt\": \"3.0.0-rc.11\"\r\n },\r\n \"dependencies\": {\r\n \"@nuxt/test-utils\": \"3.0.0-rc.11\",\r\n \"vitest\": \"^0.23.4\"\r\n }\r\n}\r\n```\r\n\r\n```ts\r\n// vite.config.ts\r\n\r\nimport { defineConfig } from \"vitest/config\";\r\n\r\nexport default defineConfig({\r\n test: {\r\n globals: true,\r\n },\r\n});\r\n```\r\n\r\n```html\r\n// pages/index.vue\r\n\r\n\u003Ctemplate>\r\n \u003Ch1>Hello World!\u003C/h1>\r\n\u003C/template>\r\n```\r\n\r\n```ts\r\n// pages/index.spec.ts\r\n\r\nimport { describe, test, expect } from 'vitest'\r\nimport { setup, $fetch } from '@nuxt/test-utils'\r\n\r\ndescribe('My test', async () => {\r\n await setup({\r\n runner: 'vitest',\r\n })\r\n\r\n test('my test', () => {\r\n const html = $fetch('/')\r\n\r\n expect(html).toContain('Hello World!')\r\n })\r\n})\r\n```\n\n### Describe the bug\n\nDuring the `beforeAll` section of the `setup` in my test it crashes with this result:\r\n\r\n```\r\nError: [vite]: Rollup failed to resolve import \"jest\" from \"node_modules/@nuxt/test-utils/dist/index.mjs\".\r\nThis is most likely unintended because it can break your application at runtime.\r\nIf you do want to externalize this module explicitly add it to\r\n`build.rollupOptions.external`\r\n```\r\n\r\nThis is strange since the runner is clearly `vitest`, so it shouldnt be trying to import jest.\r\n\r\nTook a brief look at the `index.mjs` and my `hooks.ctx.options.runner` is properly recieving `vitest`.\r\n\r\nThe error ends with:\r\n\r\n```\r\n Segmentfault Error Detected \r\n FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal.\r\n Refer to https://github.com/nodejs/node/issues/42407\r\n```\n\n### Additional context\n\nI havent been able to find a solid working example to base my own code. I was hoping this issue was just the RC version that I was using, but so far I havent had any luck with changing it. \r\n\r\nI tried cloning the `nuxt-ionic` repository as I saw it was on a later RC version and using vitest, however even with that I ran into issues. Is there a good working example I can be pointed in the direction of?\n\n### Logs\n\n```shell\n$ vitest run\r\n\r\n RUN v0.23.4 /Users/*********************/test-utils\r\n\r\n ❯ pages/index.spec.ts (1)\r\n 1: 0x103ab6ef5 node::Abort() (.cold.1) [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n ❯ pages/index.spec.ts (1) 4104ms\r\n ❯ My test (1) 4103ms\r\n ⠙ [ beforeAll ]\r\n · my test\r\n\r\n 2: 0x1027aa869 node::Abort() [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n 3: 0x1027aa9df node::OnFatalError(char const*, char const*) [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n FAIL pages/index.spec.ts > My test\r\n 4: 0x10292ed00 v8::V8::ToLocalEmpty() [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\nError: [vite]: Rollup failed to resolve import \"jest\" from \"node_modules/@nuxt/test-utils/dist/index.mjs\".\r\nThis is most likely unintended because it can break your application at runtime.\r\nIf you do want to externalize this module explicitly add it to\r\n`build.rollupOptions.external`\r\n ❯ onRollupWarning node_modules/vite/dist/node/chunks/dep-6b3a5aff.js:45908:19\r\n 5: 0x1027a596f node::fs::FSReqPromise\u003Cnode::AliasedBufferBase\u003Cdouble, v8::Float64Array, void> >::Resolve(v8::Local\u003Cv8::Value>) [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n ❯ onwarn node_modules/vite/dist/node/chunks/dep-6b3a5aff.js:45706:13\r\n ❯ Object.onwarn node_modules/vite/node_modules/rollup/dist/es/shared/rollup.js:23225:13\r\n ❯ ModuleLoader.handleResolveId node_modules/vite/node_modules/rollup/dist/es/shared/rollup.js:22352:26\r\n ❯ ModuleLoader.resolveDynamicImport node_modules/vite/node_modules/rollup/dist/es/shared/rollup.js:22404:120\r\n ❯ async file:/Users/*********************/test-utils/node_modules/vite/node_modules/rollup/dist/es/shared/rollup.js:22299:32\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n 6: 0x1027afa40 node::fs::AfterStat(uv_fs_s*) [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n 7: 0x103176598 uv__work_done [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n 8: 0x10317b75b uv__async_io [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n 9: 0x10318f54b uv__io_poll [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\nSerialized Error: Object {\r\n \"watchFiles\": [Array],\r\n}\r\n10: 0x10317bce1 uv_run [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯\r\n\r\n11: 0x1026dbf9f node::SpinEventLoop(node::Environment*) [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\nTest Files 1 failed (1)\r\n Tests (1)\r\n12: 0x102852cae node::worker::Worker::Run() [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n13: 0x1028566a2 node::worker::Worker::StartThread(v8::FunctionCallbackInfo\u003Cv8::Value> const&)::$_3::__invoke(void*) [/Users/*********************/.nvm/versions/node/v16.16.0/bin/node]\r\n14: 0x7ff8042ef4e1 _pthread_start [/usr/lib/system/libsystem_pthread.dylib]\r\n15: 0x7ff8042eaf6b thread_start [/usr/lib/system/libsystem_pthread.dylib]\r\n\r\n Segmentfault Error Detected \r\n FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal.\r\n Refer to https://github.com/nodejs/node/issues/42407\r\n\r\nIt seems to be an upstream bug of Node.js. To improve the test stability,\r\nyou could pass --segfault-retry=3 or set env VITEST_SEGFAULT_RETRY=3 to\r\nhave Vitest auto retries on flaky segfaults.\r\n\r\nerror Command failed with exit code 1.\n```\n",[3111,3112,3113],{"name":3037,"color":3038},{"name":3018,"color":3019},{"name":3054,"color":3041},15073,"Unable to get a running env with `nuxt/test-utils`","2023-01-19T17:44:36Z","https://github.com/nuxt/nuxt/issues/15073",0.68335,{"description":3120,"labels":3121,"number":3127,"owner":3027,"repository":3027,"state":3043,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### 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_",[3122,3123,3124],{"name":3037,"color":3038},{"name":3054,"color":3041},{"name":3125,"color":3126},"⛔️ 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.6852455,{"description":3133,"labels":3134,"number":3137,"owner":3027,"repository":3027,"state":3043,"title":3138,"updated_at":3139,"url":3140,"score":3141},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.3.3\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: modules\r\n- Runtime Modules: nuxt-vitest@0.6.12\r\n- Build Modules: -\n\n### Reproduction\n\nIn https://stackblitz.com/edit/github-wtj3ft-nhb1dj?file=app.spec.js,nuxt.config.ts,app.vue,vitest.config.js,package.json\r\n\r\ncreate a new terminal and run:\r\n\r\n```shell\r\nyarn run vitest\r\n```\n\n### Describe the bug\n\nhttps://nuxt.com/docs/getting-started/testing#testing states to test context option one should use `await setup`\r\n\r\nusing that setup throws the error\r\n\r\n```\r\nError while requiring module `nuxt-vitest`: TypeError [ERR_INVALID_URL]: Invalid URL\r\n```\n\n### Additional context\n\nTo migrate from nuxt2 to nuxt3 we replace fetch with `useAsyncData`. To minimise migration work we register an axios instance via a plugin to the nuxt context and return data inside `useAsyncData`\r\n\r\nIn order to mock the axios registered to `useNuxtApp()` we use the method described in https://nuxt.com/docs/getting-started/testing#testing\n\n### Logs\n\n```shell-script\nyarn run v1.22.19\r\n$ /home/projects/github-wtj3ft-nhb1dj/node_modules/.bin/vitest run\r\n\r\n RUN v0.30.1 /home/projects/github-wtj3ft-nhb1dj\r\n\r\nstdout | unknown test\r\n\u003CSuspense> is an experimental feature and its API will likely change.\r\nsetup\r\n\r\n ❯ app.spec.js (1 test) 578ms\r\nstdout | unknown test\r\n\u003Cempty line>\r\n\r\n Test Files 1 failed (1)\r\n Tests (1)\r\n Start at 15:26:17\r\n Duration 2.69s (transform 170ms, setup 0ms, collect 343ms, tests 578ms, environment 510ms, prepare 219ms)\r\n\r\ninfo Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.\n```\n",[3135,3136],{"name":3037,"color":3038},{"name":3018,"color":3019},20651,"@nuxt-vitest throws ERR_INVALID_URL when using setup() from @nuxt/test-utils in spec","2023-05-04T08:26:18Z","https://github.com/nuxt/nuxt/issues/20651",0.6888066,["Reactive",3143],{},["Set"],["ShallowReactive",3146],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZ-AYO6mcZVG5c0ks05gGpM5ODpo4IZ7AUbxEvPozCyE":-1},"/nuxt/test-utils/350"]