\n\n### Workaround\nUsing `defineVitestConfig` and hoisting the configuration up to root works fine. Unfortunately I'd need to run three Vitest tasks and couldn't make use of the `projects` functionality.\n\nFor example:\n\n```\npnpm vitest --config vitest.browser.config.ts\npnpm vitest --config vitest.unit.config.ts\npnpm vitest --config vitest.e2e.config.ts\n# 😔\n```\n\n---\n\nSo, I can't figure out how to get it working. I've tried different combinations, singular projects, and using the deprecated `workspaces` key. The method `defineVitestProject` isn't documented and I've read through the code and I'm not really sure why I'm getting an error.\n\n### Nuxt Info\n\n```\n- Operating System: `Darwin`\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@10.11.1`\n- Builder: `-`\n- User Config: `compatibilityDate`, `modules`\n- Runtime Modules: `@nuxt/test-utils/module@3.19.1`\n- Build Modules: `-`\n```\n\n### Additional information\n\n- [x] 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).",[3151],{"name":3138,"color":3139},1322,"Support Vitest `projects` option for Browser Mode","2025-06-18T13:51:03Z","https://github.com/nuxt/test-utils/issues/1322",0.6476899,{"description":3158,"labels":3159,"number":3162,"owner":3141,"repository":3141,"state":3143,"title":3163,"updated_at":3164,"url":3165,"score":3166},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.7.0\n- Nuxt Version: 4.1.0\n- CLI Version: 3.28.0\n- Nitro Version: 2.12.5\n- Package Manager: bun@1.2.21\n- Builder: -\n- User Config: compatibilityDate, devtools, ssr, telemetry, css, typescript, app, vite, hooks, nitro, runtimeConfig, modules, icon, security\n- Runtime Modules: @nuxt/eslint@1.9.0, @nuxt/scripts@0.11.10, @nuxt/ui@3.3.3, @vueuse/nuxt@13.7.0, nuxt-mikro-orm-module@0.4.1, nuxt-auth-utils@0.5.23, nuxt-security@2.4.0, nuxt-mcp@0.2.4, @nuxtjs/turnstile@1.0.0, @polar-sh/nuxt@0.3.6\n- Build Modules: -\n\n### Describe the bug\n\nI want to extend server tsconfig but i cant find the property! `nodeTsConfig`, `sharedTsConfig`, `tsConfig` are there but `serverTsConfig` not found!\n\nAlso using `tsConfig` and `nodeTsConfig` doesn't work.\n\n```\ntypescript: {\n /**\n * TypeScript comes with certain checks to give you more safety and analysis of your program. Once you’ve converted your codebase to TypeScript, you can start enabling these checks for greater safety. [Read More](https://www.typescriptlang.org/docs/handbook/migrating-from-javascript.html#getting-stricter-checks)\n *\n */\n strict: boolean;\n /**\n * Which builder types to include for your project.\n *\n * By default Nuxt infers this based on your `builder` option (defaulting to 'vite') but you can either turn off builder environment types (with `false`) to handle this fully yourself, or opt for a 'shared' option.\n * The 'shared' option is advised for module authors, who will want to support multiple possible builders.\n */\n builder: 'vite' | 'webpack' | 'rspack' | 'shared' | false | undefined | null;\n /**\n * Modules to generate deep aliases for within `compilerOptions.paths`. This does not yet support subpaths. It may be necessary when using Nuxt within a pnpm monorepo with `shamefully-hoist=false`.\n */\n hoist: Array\u003Cstring>;\n /**\n * Include parent workspace in the Nuxt project. Mostly useful for themes and module authors.\n */\n includeWorkspace: boolean;\n /**\n * Enable build-time type checking.\n *\n * If set to true, this will type check in development. You can restrict this to build-time type checking by setting it to `build`. Requires to install `typescript` and `vue-tsc` as dev dependencies.\n *\n * @see [Nuxt TypeScript docs](https://nuxt.com/docs/guide/concepts/typescript)\n */\n typeCheck: boolean | 'build';\n /**\n * You can extend the generated `.nuxt/tsconfig.app.json` (and legacy `.nuxt/tsconfig.json`) using this option.\n */\n tsConfig: 0 extends 1 & RawVueCompilerOptions ? TSConfig : TSConfig & {\n vueCompilerOptions?: RawVueCompilerOptions;\n };\n /**\n * You can extend the generated `.nuxt/tsconfig.node.json` using this option.\n */\n nodeTsConfig: TSConfig;\n /**\n * You can extend the generated `.nuxt/tsconfig.shared.json` using this option.\n */\n sharedTsConfig: TSConfig;\n /**\n * Generate a `*.vue` shim.\n *\n * We recommend instead letting the [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar) generate accurate types for your components.\n * Note that you may wish to set this to `true` if you are using other libraries, such as ESLint, that are unable to understand the type of `.vue` files.\n */\n shim: boolean;\n };\n```\n",[3160],{"name":3138,"color":3161},"E99695",33201,"`ConfigSchema.typescript` missing `serverTsConfig`","2025-09-10T23:49:48Z","https://github.com/nuxt/nuxt/issues/33201",0.65178365,{"description":3168,"labels":3169,"number":3177,"owner":3141,"repository":3141,"state":3178,"title":3179,"updated_at":3180,"url":3181,"score":3182},"### 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",[3170,3173,3174],{"name":3171,"color":3172},"3.x","29bc7f",{"name":3138,"color":3161},{"name":3175,"color":3176},"needs reproduction","FBCA04",15073,"closed","Unable to get a running env with `nuxt/test-utils`","2023-01-19T17:44:36Z","https://github.com/nuxt/nuxt/issues/15073",0.6131634,{"labels":3184,"number":3187,"owner":3141,"repository":3141,"state":3178,"title":3188,"updated_at":3189,"url":3190,"score":3191},[3185,3186],{"name":3171,"color":3172},{"name":3138,"color":3161},25203,"How should I add test to my application?","2024-01-14T22:58:03Z","https://github.com/nuxt/nuxt/issues/25203",0.6297579,{"description":3193,"labels":3194,"number":3201,"owner":3141,"repository":3142,"state":3178,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### Environment\n\n- Node Version: v20.18.1\n- Nuxt Version: 3.8.2\n- CLI Version: 3.10.0\n- Nitro Version: 2.8.1\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: ssr, experimental, runtimeConfig, modules, site, ui, colorMode, pwa, tailwindcss, i18n, viewport, imports, devtools, typescript, alias, routeRules, $production\n- Runtime Modules: @nuxtjs/google-fonts@3.1.3, @nuxt/image@1.0.0-rc.3, nuxt-schema-org@3.2.3, nuxt-icon@0.4.2, @nuxtjs/i18n@8.0.0-rc.11, nuxt-viewport@2.0.6, @nuxtjs/device@3.1.1, @nuxt/ui@2.11.1, @vueuse/nuxt@10.7.0, @vite-pwa/nuxt@0.3.5, @artmizu/nuxt-prometheus@2.4.0\n\n### Reproduction\n\n1. exec yarn add --dev @nuxt/test-utils@3.9.0\n2. yarn build\n\n### Describe the bug\n\ncheck yarn.lock, it generate this info:\nvitest-environment-nuxt@^1.0.0, vitest-environment-nuxt@^1.0.1:\n version \"1.0.1\"\n resolved \"https://registry.npmmirror.com/vitest-environment-nuxt/-/vitest-environment-nuxt-1.0.1.tgz#e3308454af1947dbc315ce2a805a9d4fe4d1c49a\"\n integrity sha512-eBCwtIQriXW5/M49FjqNKfnlJYlG2LWMSNFsRVKomc8CaMqmhQPBS5LZ9DlgYL9T8xIVsiA6RZn2lk7vxov3Ow==\n dependencies:\n \"@nuxt/test-utils\" \">=3.13.1\"\n\nI think this version default vitest-environment-nuxt@^1.0.0, and not auto import 1.0.1, it will occur compatible problem in low version\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3195,3197,3198],{"name":3175,"color":3196},"DE7793",{"name":3138,"color":3139},{"name":3199,"color":3200},"closed-by-bot","ededed",1260,"About test-utils import vitest-environment-nuxt@^1.0.1 occur compatible problem","2025-05-05T02:14:50Z","https://github.com/nuxt/test-utils/issues/1260",0.63207114,{"labels":3207,"number":3209,"owner":3141,"repository":3141,"state":3178,"title":3210,"updated_at":3211,"url":3212,"score":3213},[3208],{"name":3138,"color":3161},28608,"type checking error for globally imported vitest globals","2024-08-20T10:23:47Z","https://github.com/nuxt/nuxt/issues/28608",0.6361625,{"description":3215,"labels":3216,"number":3223,"owner":3141,"repository":3141,"state":3178,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.1\r\n- Package Manager: yarn@3.5.1\r\n- Builder: vite\r\n- User Config: extends, debug, ssr, routeRules, experimental, runtimeConfig, typescript, css, i18n, modules, alias, vite\r\n- Runtime Modules: nuxt-icon@^0.4.1, @nuxtjs/i18n@8.0.0-beta.12, @vueuse/nuxt@10.2.0, @nuxt/devtools@0.6.3, @nuxtjs/eslint-module@^4.1.0, nuxt-vitest@^0.8.5\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nAdd the nuxt-icon module with typecheck enabled.\n\n### Describe the bug\n\nEssentially a regression on: https://github.com/nuxt/nuxt/pull/20526.\r\n\r\nAs noted here: https://github.com/nuxt-modules/icon/issues/86.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3217,3220,3221,3222],{"name":3218,"color":3219},"types","2875C3",{"name":3171,"color":3172},{"name":3138,"color":3161},{"name":3175,"color":3176},21816,"Nuxt `3.6.1` introduces a regression on `AppConfig` types:","2023-09-13T13:03:57Z","https://github.com/nuxt/nuxt/issues/21816",0.63709134,{"description":3229,"labels":3230,"number":3233,"owner":3141,"repository":3141,"state":3178,"title":3234,"updated_at":3235,"url":3236,"score":3237},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `pnpm@7.18.2`\r\n- Builder: `vite`\r\n- User Config: `srcDir`, `imports`, `modules`, `css`, `build`, `pinceau`, `i18n`, `typescript`, `colorMode`, `ignore`, `vite`, `tailwindcss`, `plausible`\r\n- Runtime Modules: `@pinia/nuxt@0.4.6`, `@vueuse/nuxt@9.7.0`, `@nuxtjs/tailwindcss@6.1.3`, `@pinia/nuxt@0.4.6`, `@nuxtjs/i18n@8.0.0-beta.7`, `@nuxtjs/color-mode@3.2.0`, `@huntersofbook/plausible-nuxt@0.5.2`, `@nuxtjs/partytown@1.3.0`, `nuxt-icon@0.1.8`, `pinceau/nuxt`, `@nuxtjs/fontaine@0.2.3`, `nuxt-headlessui@1.0.4`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://github.com/productdevbook/oku-nuxt3-template/tree/bug-nuxt-config\r\n\r\nbrach: bug-nuxt-config\n\n### Describe the bug\n\n\r\nhttps://user-images.githubusercontent.com/38668796/208305787-be4c7c65-820b-4eb5-baaf-9d6295232c31.mp4\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3231,3232],{"name":3171,"color":3172},{"name":3138,"color":3161},15671,"nuxt config TS errors","2023-01-19T18:29:58Z","https://github.com/nuxt/nuxt/issues/15671",0.64193904,{"description":3239,"labels":3240,"number":3243,"owner":3141,"repository":3141,"state":3178,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.20.1\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@4.1.0\r\n- Builder: vite\r\n- User Config: srcDir, buildDir, modules, ssr, nitro, serverHandlers, css, components, imports, build, builder, typescript, vue, hooks\r\n- Runtime Modules: @nuxt/test-utils/module@3.12.0\r\n- Build Modules: -\n\n### Reproduction\n\nUnfortunately I could not reproduce this behaviour in a fresh repo.\n\n### Describe the bug\n\nUsing `defineVitestConfig` from `@nuxt/test-utils` gives me some errors on random(?) test files located in a specific folder (`./src/plugins/` in this case). It seems that vitest doesn't find those tests inside this directory (`No test suite found in file /omniweb/gsd/src/plugins/frontend-commons.spec.ts`). I tried to place a simple `test.spec.ts` inside with a basic test but it doesn't pick that up either.\r\nHowever if I move those test files to another directory at the same level it runs those test. If I rename the folder to `plugins` it again does not run those test files...\r\n\r\nI really can't imagine what's going on here. Are there some forbidden path patterns for some reason?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3241,3242],{"name":3171,"color":3172},{"name":3138,"color":3161},26898,"`defineVitestConfig` from `@nuxt/test-utils` is not a drop-in replacement for `defineConfig` from `vite` (`No test suite found in file`)","2024-04-23T07:13:27Z","https://github.com/nuxt/nuxt/issues/26898",0.6439419,["Reactive",3249],{},["Set"],["ShallowReactive",3252],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2TkqNOpZQ76rZOVumhpa3E0IiPT_a24F-b9lzTnhcKI":-1},"/nuxt/test-utils/1296"]