\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).",[3031],{"name":3018,"color":3019},1322,"Support Vitest `projects` option for Browser Mode","2025-06-18T13:51:03Z","https://github.com/nuxt/test-utils/issues/1322",0.6655597,{"description":3038,"labels":3039,"number":3041,"owner":3021,"repository":3022,"state":3023,"title":3042,"updated_at":3043,"url":3044,"score":3045},"### Environment\n\n\n\"@nuxt/test-utils\": \"^3.19.2\",\n\"vitest\": \"^3.2.3\"\n\n--\n- Operating System: Windows_NT\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: runtimeConfig, ssr, alias, compatibilityDate, devtools, css, vite, modules\n- Runtime Modules: @nuxt/test-utils/module@3.19.2, @pinia/nuxt@0.11.1\n- Build Modules: -\n\n### Reproduction\n\nSimilar to [here](https://stackoverflow.com/questions/79537445/not-all-components-impacted-by-coverage).\nIst about the nuxt environment.\nI changed it from `happy-dom` to `nuxt`. Since then it is not coverging pages.\nThe Stackoverflow user had a much simpler set up without projects.\n\n```ts\nimport {\n defineVitestConfig,\n defineVitestProject,\n} from \"@nuxt/test-utils/config\";\nimport vue from \"@vitejs/plugin-vue\";\nimport AutoImport from \"unplugin-auto-import/vite\";\nimport { configDefaults, defineConfig } from \"vitest/config\";\n\n// 1️⃣ Nuxt-specific setup via defineVitestConfig\nconst nuxtConfig = defineVitestConfig({\n test: {\n environment: \"nuxt\",\n globals: true,\n },\n});\n\n// 2️⃣ Full Vitest config using core defineConfig\nexport default defineConfig({\n ...nuxtConfig,\n test: {\n coverage: {\n provider: \"v8\",\n reporter: [\"text\", \"json\", \"html\"],\n reportsDirectory: \"./tests/coverage\",\n exclude: [\n ...(configDefaults.coverage?.exclude ?? []),\n \"**/*.cy.ts\",\n \"**/*.cy.tsx\",\n \"**/cypress/**\",\n \"nuxt.config.ts\",\n \"scripts/**\",\n ],\n thresholds: { statements: 90, branches: 90, functions: 0, lines: 90 },\n },\n\n projects: [\n {\n test: {\n name: \"Server (Node Environment)\",\n include: [\"tests/server/**/*.{test,spec}.ts\"],\n globals: true,\n environment: \"node\",\n },\n plugins: [vue(), AutoImport({ imports: [\"vue\"], dts: true })],\n },\n await defineVitestProject({\n test: {\n name: \"Happy NUXT Environment\",\n include: [\n \"tests/pages/**/*.{test,spec}.ts\",\n \"tests/components/**/*.{test,spec}.ts\",\n \"tests/composables/**/*.{test,spec}.ts\",\n \"tests/utils/**/*.{test,spec}.ts\",\n \"tests/plugins/**/*.{test,spec}.ts\",\n \"tests/layouts/**/*.{test,spec}.ts\",\n \"tests/directives/**/*.{test,spec}.ts\",\n \"tests/mixins/**/*.{test,spec}.ts\",\n \"tests/app.test.ts\",\n \"Tests/error.test.ts\",\n ],\n exclude: [\"tests/server/*.{test,spec}.ts\"],\n globals: true,\n environment: \"nuxt\",\n setupFiles: [\"./tests/setup.ts\"],\n },\n }),\n ],\n },\n});\n```\n\n### Describe the bug\n\nnuxt environment doesn't create coverage for pages\n\n\n\n\n### Additional context\n\nI tried additionally and explicitly adding pages to includes. But it doesn't work.\nPlease, tag me, if it requires to be opened up in a different repository, such as vitest.\n\n### Logs\n\n```shell-script\n\n```",[3040],{"name":3018,"color":3019},1352,"pages are not covered in nuxt environment","2025-07-07T13:56:40Z","https://github.com/nuxt/test-utils/issues/1352",0.6743779,{"description":3047,"labels":3048,"number":3051,"owner":3021,"repository":3021,"state":3023,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Environment\r\n\r\nLatest pnpm\r\n\r\nWorking directory: /home/projects/nuxt-starter-qea1r5/packages/apps/my-app 5:21:21 PM\r\nNuxt project info: 5:21:21 PM\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.1\r\n- CLI Version: 3.8.0\r\n- Nitro Version: 2.6.2\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: extends\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new 5:21:21 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\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-qea1r5\r\n\r\n* Environment set to use `export npm_config_shared_workspace_lockfile=false`\r\n* `FORCE_COLOR=1 pnpm --stream --filter ./packages/apps/my-app dev` to run.\r\n\r\nHowever, if using shared lock-file (default setting), there is no dep issue:\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-jgqtiw\r\n\r\n### Describe the bug\r\n\r\nUsing a pnpm monorepo, layers and/or modules from filesystem workspace, which have dependencies, no longer build correctly after upgrading to 3.7.1, in both dev and production build.\r\n\r\nSince trying ^3.7.0, i get this error now:\r\n\r\n`[nuxt] Could not resolve id yup /workspace/packages/my-app/index.html`\r\n\r\n1) i have a module which includes a dependency (yup)\r\n2) And a component in the module uses this dependency (yup)\r\n3) module auto-imports the component.\r\n4) my-app uses the module from the pnpm workspace\r\n5) now getting this error on my-app startup (pnpm dev)\r\n\r\nThis worked fine in 3.6.5, and is a breaking change\r\n\r\ni moved from using a module to using a layer:\r\n\r\n1) Layer has dep for yup\r\n2) Layer Component imports yup\r\n3) App extends layer\r\n4) App uses layer component\r\n5) [nuxt] Could not resolve id yup /workspace/packages/my-app/index.html\r\n\r\nHappens both as \"dependency\" or \"devDependency\".\r\n\r\nHappens if using `\u003Cscript setup>` or just `\u003Cscript>`.\r\n\r\nOnly works if i install yup directly in my-app (which is unacceptable.)\r\n\r\n### Additional context\r\n\r\nDOES NOT work:\r\n\r\n\r\n\r\nWORKS:\r\n\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[3049],{"name":3018,"color":3050},"E99695",23077,"3.7.x: shared-workspace-lockfile=false now breaks monorepo deps (via layers/modules) (!!)","2024-06-30T11:07:43Z","https://github.com/nuxt/nuxt/issues/23077",0.67728925,{"description":3057,"labels":3058,"number":3063,"owner":3021,"repository":3021,"state":3064,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v19.3.0`\r\n- Nuxt Version: `3.8.0`\r\n- CLI Version: `3.9.1`\r\n- Nitro Version: `2.7.2`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `-`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/halilyuce/monorepo\r\n\r\n### Describe the bug\r\n\r\nHere is my monorepo structure:\r\n\r\n\u003Cimg width=\"297\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/29376592/7a1f6640-6b7b-4f63-aa0e-62adce755b01\">\r\n\r\nI created a monorepo with npm workspaces and extended apps in the portal(main app) thanks to nuxt layers. Everything works as expected in production mode but not in dev mode?\r\n\r\nWhen I run the project in dev mode, I do not receive any errors. It stays on the nuxt loading screen and the computer starts to heat up seriously and the fans become loud, probably a memory problem. \r\n\r\nI have a decent laptop, according to my research, this problem occurs because the node_modules location changes when using monorepo. I applied dozens of solutions for this, but none of them worked.\r\n\r\n\u003Cimg width=\"454\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/29376592/cd338d5c-9071-43a9-9006-3e25e82f2169\">\r\n\r\n\r\n\r\n\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_",[3059,3062],{"name":3060,"color":3061},"3.x","29bc7f",{"name":3018,"color":3050},24049,"closed","Nuxt Layers + Npm Workspaces(Monorepo) Doesn't work only in Dev Mode","2023-10-31T21:23:22Z","https://github.com/nuxt/nuxt/issues/24049",0.629651,{"description":3070,"labels":3071,"number":3073,"owner":3021,"repository":3022,"state":3064,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: -\n- CLI Version: 3.25.1\n- Nitro Version: -\n- Package Manager: pnpm@10.11.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://github.com/daugvinasr/nuxt-repro\n\n### Describe the bug\n\nInside a monorepo `nuxt/test-utils` ignores provided runner (`jsdom`) and always defaults to `happy-dom`.\n\nvitest.config.ts\n```ts\nimport { defineVitestConfig } from '@nuxt/test-utils/config'\n\nexport default defineVitestConfig({\n test: {\n runner: 'jsdom',\n include: ['**\\/*.{test,spec}.?(c|m)[jt]s?(x)']\n }\n})\n```\n\n### Logs\n\n```shell-script\n➜ nuxt-repro git:(main) pnpm --filter iframe test\n\n> iframe@ test /Users/daugvinas/Projects/nuxt-repro/apps/iframe\n> vitest\n\n\n DEV v3.1.4 /Users/daugvinas/Projects/nuxt-repro/apps/iframe\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\nVitest caught 1 unhandled error during the test run.\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\nTypeError: TestRunner is not a constructor\n ❯ resolveTestRunner ../../node_modules/.pnpm/vitest@3.1.4_@types+node@22.15.19_jiti@2.4.2_jsdom@26.1.0_terser@5.39.2_yaml@2.8.0/node_modules/vitest/dist/chunks/index.Cu2UlluP.js:38:21\n ❯ processTicksAndRejections node:internal/process/task_queues:105:5\n ❯ run ../../node_modules/.pnpm/vitest@3.1.4_@types+node@22.15.19_jiti@2.4.2_jsdom@26.1.0_terser@5.39.2_yaml@2.8.0/node_modules/vitest/dist/chunks/runBaseTests.BV8m0B-u.js:106:17\n ❯ runBaseTests ../../node_modules/.pnpm/vitest@3.1.4_@types+node@22.15.19_jiti@2.4.2_jsdom@26.1.0_terser@5.39.2_yaml@2.8.0/node_modules/vitest/dist/chunks/base.DslwPSCy.js:35:2\n ❯ ForksBaseWorker.executeTests ../../node_modules/.pnpm/vitest@3.1.4_@types+node@22.15.19_jiti@2.4.2_jsdom@26.1.0_terser@5.39.2_yaml@2.8.0/node_modules/vitest/dist/workers/forks.js:27:4\n ❯ execute ../../node_modules/.pnpm/vitest@3.1.4_@types+node@22.15.19_jiti@2.4.2_jsdom@26.1.0_terser@5.39.2_yaml@2.8.0/node_modules/vitest/dist/worker.js:113:3\n ❯ onMessage ../../node_modules/.pnpm/tinypool@1.0.2/node_modules/tinypool/dist/entry/process.js:55:20\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n\n Test Files (1)\n Tests no tests\n Errors 1 error\n Start at 10:09:06\n Duration 331ms (transform 21ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 0ms)\n\n FAIL Tests failed. Watching for file changes...\n press h to show help, press q to quit\n```",[3072],{"name":3018,"color":3019},1300,"Inside a monorepo `nuxt/test-utils` ignores provided runner","2025-05-20T17:36:03Z","https://github.com/nuxt/test-utils/issues/1300",0.65963566,{"labels":3079,"number":3081,"owner":3021,"repository":3021,"state":3064,"title":3082,"updated_at":3083,"url":3084,"score":3085},[3080],{"name":3018,"color":3050},28608,"type checking error for globally imported vitest globals","2024-08-20T10:23:47Z","https://github.com/nuxt/nuxt/issues/28608",0.66107684,{"labels":3087,"number":3096,"owner":3021,"repository":3021,"state":3064,"title":3097,"updated_at":3098,"url":3099,"score":3100},[3088,3089,3090,3093],{"name":3060,"color":3061},{"name":3018,"color":3050},{"name":3091,"color":3092},"needs reproduction","FBCA04",{"name":3094,"color":3095},"layers","006B75",25230,"Wrong tsconfig when operating in monorepo","2024-05-24T14:00:23Z","https://github.com/nuxt/nuxt/issues/25230",0.6611241,{"description":3102,"labels":3103,"number":3106,"owner":3021,"repository":3021,"state":3064,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Environment\r\n\r\n## Monorepo root\r\n```\r\n------------------------------\r\n- Operating System: `Linux`\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@8.1.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n## App and Layer\r\n```\r\n------------------------------\r\n- Operating System: `Linux`\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@8.1.0`\r\n- Builder: `vite`\r\n- User Config: `extends`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\n1. clone this example https://github.com/kleinpetr/nuxt-layers\r\n2. run `pnpm i` in the root (it runs `nuxt prepare` at the end)\r\n3. open `layers/my-layer/nuxt.config.ts` (you should see the error as below)\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nI am playing with Nuxt Layers and facing some troubles, especially with auto imports inside layers \r\n\r\nwhen I run `pnpm build` or even `nuxi prepare` the error message disappears for a while but then returns back as you can see on the gif below\r\n\r\n\r\n\r\nI am using Volar TS Exntension with Takeover mode (I also tried enable builtin TS Language Extension and Disable Volar, but the result is still the same) \r\n\r\nDo you have any suggestion what should be the problem? (in the `/app` folder everything works fine, but inside `/layers` it is not)\r\n\r\nThanks for help :pray: \r\n\r\n### Additional context\r\nDiscussion: https://github.com/nuxt/nuxt/discussions/19963\r\nOS: Linux Fedora 37\r\nVSCode: version 1.76.2\r\n\r\n### Logs\r\n\r\n_No response_",[3104,3105],{"name":3060,"color":3061},{"name":3018,"color":3050},20155,"Nuxt Layers - VSCode auto-imports","2024-02-22T08:27:01Z","https://github.com/nuxt/nuxt/issues/20155",0.6629824,{"description":3112,"labels":3113,"number":3117,"owner":3021,"repository":3021,"state":3064,"title":3118,"updated_at":3119,"url":3120,"score":3121},"### 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",[3114,3115,3116],{"name":3060,"color":3061},{"name":3018,"color":3050},{"name":3091,"color":3092},15073,"Unable to get a running env with `nuxt/test-utils`","2023-01-19T17:44:36Z","https://github.com/nuxt/nuxt/issues/15073",0.665859,["Reactive",3123],{},["Set"],["ShallowReactive",3126],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJlItjraV5XMRKHhs8j1Q0uG14H28lqyIjcm9i2kF9mA":-1},"/nuxt/test-utils/1307"]