\n\u003C!-- OR -->\n\u003CIcon name=\"my-icon:a\" v-if=\"flag\" />\n\u003CIcon name=\"my-icon:b\" v-else />\n```\nin `nuxt.config.ts`\n```ts\nicon: {\n provider: 'server',\n customCollections: [\n {\n prefix: 'my-icon',\n dir: './assets/icon/svg',\n },\n ],\n},\n// ...\nnitro: {\n preset: 'static',\n},\n```\n\nIf toggle value of `flag`, \neverything works well in development, \nbut it throws 404 error for `my-icon:b` after building and generating.\n(it works well with `v-show`) \n\nProject info:\n```\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v22.8.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.0\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.9.0\n- Builder: -\n- User Config: modules, icon, colorMode, shadcn, fonts, googleSignIn, app, imports, css, vite, nitro, compatibilityDate, telemetry\n- Runtime Modules: @nuxtjs/tailwindcss@6.13.2, @nuxt/icon@1.11.0, @nuxt/fonts@0.11.0, @nuxt/image@1.9.0, @nuxt/eslint@1.2.0, @pinia/nuxt@0.10.1, pinia-plugin-persistedstate/nuxt@4.2.0, @nuxt/test-utils/module@3.17.2, @nuxtjs/color-mode@3.5.2, shadcn-nuxt@1.0.3, @vueuse/nuxt@13.0.0, nuxt-vue3-google-signin@0.0.11\n- Build Modules: -\n------------------------------\n```\n",[],380,"nuxt","icon","open","Local icon 404 after `nuxi generating` if with `:name=\"flag?'my-icon:icon-a':'my-icon:icon-b'\"`","2025-03-26T15:31:52Z","https://github.com/nuxt/icon/issues/380",0.7112771,{"description":1993,"labels":1994,"number":1998,"owner":1985,"repository":1999,"state":2000,"title":2001,"updated_at":2002,"url":2003,"score":2004},"Regression between v0.8.0 and v0.9.0. Potential culprit: https://github.com/nuxt/fonts/issues/266\r\n\r\nAfter upgrading to v0.9.0, a statically generated project (using `nuxt generate`) is no longer getting fonts deployed to the `_fonts/` dir (in fact, the directory does not exist).\r\n\r\nEnvironment:\r\n- `nuxt v3.12.1`\r\n- `pnpm v9.11.0`\r\n- `nuxt/fonts v0.9.0`\r\n- build and runtime environment: netlify static site\r\n\r\nDowngrading to v0.8.0 fixes the issue.\r\n",[1995],{"name":1996,"color":1997},"bug","d73a4a",284,"fonts","closed","no _fonts dir deployed on cloud provider (netlify)","2024-09-25T18:17:33Z","https://github.com/nuxt/fonts/issues/284",0.4524252,{"description":2006,"labels":2007,"number":2015,"owner":1985,"repository":1985,"state":2000,"title":2016,"updated_at":2017,"url":2018,"score":2019},"### Environment\r\n\r\n- Nuxt Version: `3.0.0-rc.13`\r\n- `@nuxt/test-utils-edge` Version: `latest(3.0.0-rc.14-27796957.b60f136)`\r\n- Vitest Version: `^0.24.0`\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-raxmub-uprd1m?file=package.json\r\n\r\n### Describe the bug\r\n\r\nWith `vitest@^0.24.0` or the latest `0.25.0`, `nuxt test` will fail, and the following error occurs:\r\n```\r\nCannot find module '/path/to/project/node_modules/vitest/dist/node.mjs' imported from /path/to/project/node_modules/@nuxt/test-utils-edge/dist/index.mjs\r\n```\r\n\r\nWe should import `vitest/dist/node.js` rather than `vitest/dist/node.mjs`.\r\n\r\n### Additional context\r\n\r\nThe extension once changed to `.mjs` in https://github.com/vitest-dev/vitest/commit/692ad34 , but in https://github.com/vitest-dev/vitest/pull/1411 it was reverted and now using `.js`.\r\n\r\n[This PR(vitest-dev/vitest#1411)](https://github.com/vitest-dev/vitest/pull/1411) was merged and released as `v0.24.0` so using `v0.23.4` or former can also resolve this issue, but I can't see it as the best way.\r\n\r\n### Logs\r\n\r\n_No response_",[2008,2011,2012],{"name":2009,"color":2010},"3.x","29bc7f",{"name":1996,"color":1997},{"name":2013,"color":2014},"chore","D0F1A9",15404,"`@nuxt/test-utils-edge` doesn't work with `vitest` v0.24.0 or later","2023-01-19T17:49:44Z","https://github.com/nuxt/nuxt/issues/15404",0.6704079,{"description":2021,"labels":2022,"number":2026,"owner":1985,"repository":2027,"state":2000,"title":2028,"updated_at":2029,"url":2030,"score":2031},"If I do not include a `nuxt.condfig.ts` in my root and configure vitest like so:\r\n```\r\nimport { fileURLToPath } from 'node:url'\r\nimport { defineVitestConfig } from 'nuxt-vitest/config'\r\n\r\nexport default defineVitestConfig({\r\n test: {\r\n coverage: {\r\n reportsDirectory: '../coverage',\r\n provider: 'c8',\r\n include: ['src/**'],\r\n exclude: ['src/**/*.spec.ts', 'src/**/*.test.ts', 'src/**/*.d.ts'],\r\n all: true\r\n },\r\n environmentOptions: {\r\n nuxt: {\r\n rootDir: fileURLToPath(new URL('./playground', import.meta.url))\r\n }\r\n },\r\n resolveSnapshotPath (path: string, extension: string) {\r\n return path + extension\r\n },\r\n setupFiles: ['./setup.ts']\r\n }\r\n})\r\n```\r\n\r\nI get\r\n```\r\nError: Failed to load nuxt-vitest module. You may need to add it to your nuxt.config.\r\n```\r\n\r\nWhere there is a nuxt config in my module's playground which includes `nuxt-vitest`",[2023],{"name":2024,"color":2025},"vitest-environment","b60205",574,"test-utils","allow configuring nuxt rootDir and overrides does not appear to work","2023-12-02T00:27:09Z","https://github.com/nuxt/test-utils/issues/574",0.67572486,{"labels":2033,"number":2044,"owner":1985,"repository":1985,"state":2000,"title":2045,"updated_at":2046,"url":2047,"score":2048},[2034,2035,2038,2041],{"name":2009,"color":2010},{"name":2036,"color":2037},"vite","3574D1",{"name":2039,"color":2040},"webpack","650C6F",{"name":2042,"color":2043},"test","1DB6E0",13426,"Tests for `nuxt:dynamic-base-path`","2023-01-19T16:55:41Z","https://github.com/nuxt/nuxt/issues/13426",0.68622273,{"description":2050,"labels":2051,"number":2053,"owner":1985,"repository":2027,"state":2000,"title":2054,"updated_at":2055,"url":2056,"score":2057},"Hey guys, today I upgraded `vitest` and `nuxt-vitest` to version [0.29.2](https://github.com/vitest-dev/vitest/releases/tag/v0.29.2) and [0.6.8](https://github.com/danielroe/nuxt-vitest/releases/tag/0.6.8), respectively.\r\n\r\nI upgraded `nuxt-vitest` because I upgraded `vitest` and installed `c8` for test coverage and I started getting the following error message on test runs:\r\n```\r\nError: Cannot find module 'vitest-environment-nuxt/module'\r\n```\r\n\r\nAnd after the `nuxt-vitest` upgrade, I started getting the following error:\r\n```\r\nError: Cannot find import \"useI18n\" to mock\r\n```\r\n\r\nAnd this happens when I try to mock `useI18n` (from `@nuxtjs/i18n`), which exists globally in my application:\r\n```javascript\r\nimport { mockNuxtImport } from 'nuxt-vitest/utils'\r\n\r\nmockNuxtImport('useI18n', () => {\r\n return () => {\r\n return {\r\n t: vi.fn()\r\n }\r\n }\r\n})\r\n```\r\n\r\nBefore all these upgrades, the mock was working properly.\r\nAnyone else with a similar problem?\r\n\r\n*EXTRA INFORMATION*\r\nOn the other hand...\r\nMy original approach to mock i18n started to work (didn't work before):\r\n```javascript\r\nimport { useI18n } from 'vue-i18n'\r\nimport { vi } from 'vitest'\r\n\r\nvi.mock('vue-i18n')\r\n\r\nuseI18n.mockReturnValue({\r\n t: (tKey) => tKey\r\n})\r\n```\r\nAnd I using this approach for now. And why it didn't work before is a mystery...",[2052],{"name":2024,"color":2025},508,"`mockNuxtImport` failing to mock Nuxt auto imports","2023-12-02T00:22:09Z","https://github.com/nuxt/test-utils/issues/508",0.6880649,{"description":2059,"labels":2060,"number":2065,"owner":1985,"repository":1985,"state":2000,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.12.2\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: default\n- Runtime Modules: subpath-demo/mod\n- Build Modules: -\n\n### Reproduction\nhttps://codesandbox.io/p/devbox/bold-moon-4f3lll?workspaceId=02247d38-3c4c-4910-9e35-fabf9385962a\n\n[module's code](https://github.com/shunnNet/demo-nuxt-module-subpath-issue)\n\n### Describe the bug\n\nA Nuxt module can be installed via a package subpath, which allows it to differ from the actual directory structure, such as:\n\n```json\n{\n \"exports\": {\n \"./mod\": {\n \"types\": \"./packages/mod/dist/types.d.ts\",\n \"import\": \"./packages/mod/dist/module.mjs\",\n \"require\": \"./packages/mod/dist/module.cjs\"\n }\n }\n}\n```\n\nWhen installed through this subpath, although the module was successfully installed, the Nuxt module's runtime code (e.g: Nuxt plugin) encounters errors when import from aliases e.g: `#app`. \n\n```ts\nexport default defineNuxtConfig({\n // omit\n modules: [\n \"subpath-demo/mod\"\n ],\n})\n```\n\n```ts\nimport { defineNuxtPlugin } from \"#app\"; // \u003C--- will fail\nexport default defineNuxtPlugin((_nuxtApp) => {\n console.log(\"Plugin injected by my-module!\");\n});\n```\n\nThis may be related to how Vite `ssr.noExternal` is configured. \n\nCurrently, Nuxt directly sets it to the user-provided string (`subpath-demo/mod`), but imports plugins using the full absolute path. ( `..... /node_modules/subpath-demo/packages/mod/dist/module.mjs`), which is not match. And dependencies will be externalized by Vite if it wasn't included in `ssr.noExternal`. [vite ssr-external](https://vite.dev/guide/ssr.html#ssr-externals)\n\nTherefore, when the subpath differs from the actual path, Vite excludes it from compilation.\n\n\n## Workaround\n1. Align subpath with actual path\n\n2. Manually add package name to `ssr.noExternal`\n\n```ts\nexport default defineNuxtConfig({\n // omit\n modules: [\n \"subpath-demo/mod\"\n ],\n vite: {\n ssr: { \n noExternal: [ \"subpath-demo\" ] \n }\n }\n})\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n```\nERROR [nuxt] [request error] [unhandled] [500] Package import specifier \"#app\" is not defined in package /Users/net/repository/test-mod-dep/node_modules/.pnpm/subpath-demo@https+++codeload.github.com+shunnNet+demo-nuxt-module-subpath-issue+tar.gz+f5f70_gfo3iqyqpkpaqjbz4jtbsmbv6e/node_modules/subpath-demo/package.json imported from /Users/net/repository/test-mod-dep/node_modules/.pnpm/subpath-demo@https+++codeload.github.com+shunnNet+demo-nuxt-module-subpath-issue+tar.gz+f5f70_gfo3iqyqpkpaqjbz4jtbsmbv6e/node_modules/subpath-demo/packages/mod/dist/runtime/plugin.js\n at importNotDefined (node:internal/modules/esm/resolve:291:10) \n at packageImportsResolve (node:internal/modules/esm/resolve:741:9) \n at moduleResolve (node:internal/modules/esm/resolve:917:16) \n at defaultResolve (node:internal/modules/esm/resolve:1157:11) \n at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:390:12) \n at ModuleLoader.resolve (node:internal/modules/esm/loader:359:25) \n at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:234:38) \n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/module_job:87:39) \n at link (node:internal/modules/esm/module_job:86:36)\n```",[2061,2062],{"name":1996,"color":1997},{"name":2063,"color":2064},"🔨 p3-minor","FBCA04",29735,"Occur error when module path is a package subpath that does not match the actual path","2024-12-03T13:20:01Z","https://github.com/nuxt/nuxt/issues/29735",0.69378394,{"labels":2071,"number":2079,"owner":1985,"repository":1985,"state":2000,"title":2080,"updated_at":2081,"url":2082,"score":2083},[2072,2075,2076],{"name":2073,"color":2074},"enhancement","8DEF37",{"name":2009,"color":2010},{"name":2077,"color":2078},"kit","60E14C",13153,"`importNuxt` uitlity","2024-06-17T15:36:41Z","https://github.com/nuxt/nuxt/issues/13153",0.70490015,{"description":2085,"labels":2086,"number":2091,"owner":1985,"repository":1985,"state":2000,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### Environment\r\n\r\nENV\r\nos: Darwin\r\nnodejs: 20.9.0\r\nnuxt: 3.8.1\r\n@nuxt/test-utils: 3.8.1\r\nvitest: 1.1.1\r\nyarn: 1.15.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-rx4vx2?file=package.json,testUtils.js,testUtils.test.js\r\n\r\nyou can run test command below.\r\n```\r\nnpm test\r\n``` \r\n\r\n### Describe the bug\r\n\r\nHello, I am using Vitest for testing on Nuxt3, vite env.\r\nDue to our team's convention, the configuration uses 'autoImport: false'.(For an explicit declaration) So when importing Nuxt's built-in items (useRoute, nextTick, computed, etc.) we use import '#imports'.\r\n\r\nWhen I run Vitest, the following error occurs:\r\n\r\nError: Failed to resolve import \"#imports\" from \"[file path]\". Does the file exist?\r\nHow do I solve this? help.\r\nIs this something that needs to be fixed in vitest?\r\n(I registered an issue on vitest. https://github.com/vitest-dev/vitest/issues/4853)\r\n(https://github.com/nuxt/nuxt/discussions/24719)\r\n\r\nBelow is my vitest.config.js\r\n```javascript\r\nimport path from 'path';\r\nimport vue from '@vitejs/plugin-vue';\r\n\r\nexport default {\r\n plugins: [vue()],\r\n test: {\r\n globals: true,\r\n environment: 'jsdom'\r\n },\r\n resolve: {\r\n alias: {\r\n '@': path.resolve(__dirname, './src')\r\n }\r\n }\r\n};\r\n``` \r\n\r\nThanks.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2087,2088],{"name":2009,"color":2010},{"name":2089,"color":2090},"pending triage","E99695",25021,"Vitest can't resolve import '#imports'(Nuxt3, vitest)","2024-06-21T04:50:44Z","https://github.com/nuxt/nuxt/issues/25021",0.7063588,{"description":2097,"labels":2098,"number":2103,"owner":1985,"repository":1985,"state":2000,"title":2104,"updated_at":2105,"url":2106,"score":2107},"### 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",[2099,2100,2101],{"name":2009,"color":2010},{"name":2089,"color":2090},{"name":2102,"color":2064},"needs reproduction",15073,"Unable to get a running env with `nuxt/test-utils`","2023-01-19T17:44:36Z","https://github.com/nuxt/nuxt/issues/15073",0.70775294,["Reactive",2109],{},["Set"],["ShallowReactive",2112],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"9cM3aiv1fj2dWYwT774gUlL6JnqprNOQYP-tIO9sMGI":-1},"/nuxt/test-utils/284"]