\n\n\u003Cimg width=\"422\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/10035094-1291-49d4-969a-c04e8a428e79\" />\n\nRequested Feature\nI would like the module to support recursive searching in customCollections directories, allowing it to find icons in all nested subdirectories like wor\n\nSteps to Reproduce\nhttps://stackblitz.com/edit/github-monhzc",[],374,"nuxt","icon","open","Feature Request: Recursive search in customCollections directories","2025-03-19T11:15:14Z","https://github.com/nuxt/icon/issues/374",0.776642,{"description":2876,"labels":2877,"number":2887,"owner":2868,"repository":2888,"state":2870,"title":2889,"updated_at":2890,"url":2891,"score":2892},"Currently, it's possible to mock a Nuxt import:\r\n\r\n```js\r\nmockNuxtImport('useStorage', () => {\r\n return vi.fn()\r\n})\r\n```\r\n\r\nWhen we want to access this mock in our test, to run an assertion or to change the implementation, we can use `vi.hoisted`:\r\n\r\n```js\r\nconst { useStorageMock } = vi.hoisted(() => {\r\n return {\r\n useStorageMock: vi.fn()\r\n }\r\n})\r\n\r\nmockNuxtImport('useStorage', () => {\r\n return useStorageMock\r\n})\r\n\r\n// now we can change the implementation of useStorageMock between tests\r\n```\r\n\r\nThis is a lot of code just to define and expose a single mock. Would it be possible to make mocking Nuxt imports easier by returning the mocks directly in `mockNuxtImport`? \r\n\r\nI propose something like this:\r\n\r\n```js\r\nconst useStorageMock = mockNuxtImport('useStorage', () => {\r\n return vi.fn()\r\n})\r\n\r\n// now we can change the implementation of useStorageMock between tests\r\n```\r\n\r\nI'm down to have a look at this if this is possible.",[2878,2881,2884],{"name":2879,"color":2880},"enhancement","a2eeef",{"name":2882,"color":2883},"good first issue","7057ff",{"name":2885,"color":2886},"vitest-environment","b60205",541,"test-utils","Expose mocks directly with `mockNuxtImport`","2024-05-01T17:46:01Z","https://github.com/nuxt/test-utils/issues/541",0.7819676,{"description":2894,"labels":2895,"number":2899,"owner":2868,"repository":2900,"state":2870,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### 📚 Is your documentation request related to a problem?\n\n📚 Is your documentation request related to a problem?\n\nI couldn't find in the docs how to display in the devtools so that I can know which one is which.\n\n```ts\n useScript(\n {\n src: \"xxx\",\n id: \"super-script-src\",\n },\n {\n devtools: {\n registryKey: \"SuperScript\", // Key used to map to the registry script for Nuxt DevTools. as per JS Docs ( It's not the name \n registryMeta: {\n name: \"SuperScript\", // We can include here for example the name\n },\n },\n },\n );\n```\n\nExample after I included that meta data in the devtools\n\n\n\n\n\n### 🔍 Where should you find it?\n\nI would say a tab with devtools in the sidebar with this and more information on how useful the devtools is, would be really important\n\n### ℹ️ Additional context\n\n_No response_",[2896],{"name":2897,"color":2898},"documentation","0075ca",332,"scripts","How to display in the devtools name of the scripts","2024-12-06T09:14:08Z","https://github.com/nuxt/scripts/issues/332",0.7871677,{"description":2906,"labels":2907,"number":2910,"owner":2868,"repository":2911,"state":2912,"title":2913,"updated_at":2914,"url":2915,"score":2916},"- [x] Create new file\n- [ ] Upload new file\n- [x] Rename\n- [x] Revert\n- [x] Delete",[2908],{"name":2879,"color":2909},"1ad6ff",347,"nuxt.com","closed","Files actions specific to current page (`content` / `media`)","2023-02-15T12:32:11Z","https://github.com/nuxt/nuxt.com/issues/347",0.4476654,{"description":2918,"labels":2919,"number":2924,"owner":2868,"repository":2911,"state":2912,"title":2925,"updated_at":2926,"url":2927,"score":2928},"- [x] Remove action dropdown in media items\n- [x] `Branch` and `File` modal buttons should go into root menu at the bottom\n- [x] `Create file` / `Upload file` should go in navbar dialog tree header right\n- [x] `ProjectNavbar` should contain the name of the file and the `Save` / `Publish` / `Preview` (only icon) buttons\n- [x] `ProjectNavbar` online users disappears for now\n- [x] Next to filename in `ProjectNavbar` we should have a `chevron-down` icon to extend the desktop aside panel with: file actions (`Rename` / `Revert` / `Delete`) and tabs (`Meta` / `History`) and `chevron-up` icon to collapse the menu",[2920,2921],{"name":2879,"color":2909},{"name":2922,"color":2923},"responsive","1cd1c6",642,"[Project] Content + Media responsive files aside","2023-02-15T12:32:40Z","https://github.com/nuxt/nuxt.com/issues/642",0.70917255,{"description":2930,"labels":2931,"number":2924,"owner":2868,"repository":2888,"state":2912,"title":2935,"updated_at":2936,"url":2937,"score":2928},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v18.11.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@8.19.2\r\n- Builder: -\r\n- User Config: devtools, app, css, modules, runtimeConfig\r\n- Runtime Modules: nuxt-icon-tw@0.1.3, @nuxtjs/tailwindcss@6.10.1, @nuxtjs/i18n@8.0.0-rc.9\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n A lot of the recent fixes done seem to only work on the main branch it seems, but i'm unable to install it with npm\r\n \r\n `npm install -D \"https://github.com/nuxt/test-utils.git#main\"`\r\n\r\n### Describe the bug\r\n\r\n````\r\nnpm ERR! code ETARGET\r\nnpm ERR! notarget No matching version found for @nuxt/test-utils@>=3.9.0.\r\nnpm ERR! notarget In most cases you or one of your dependencies are requesting\r\nnpm ERR! notarget a package version that doesn't exist.\r\n````\r\n\r\n### Additional context\r\n\r\nWhat is the recommended way to run the main branch?\r\n\r\n### Logs\r\n\r\n_No response_",[2932],{"name":2933,"color":2934},"pending triage","5D08F5","Unable to install main branch","2023-12-12T13:29:02Z","https://github.com/nuxt/test-utils/issues/642",{"description":2939,"labels":2940,"number":2942,"owner":2868,"repository":2911,"state":2912,"title":2943,"updated_at":2944,"url":2945,"score":2946},"As for branches, we'll need to reload the cache.",[2941],{"name":2879,"color":2909},325,"Refresh files action in files modal","2023-02-15T12:32:08Z","https://github.com/nuxt/nuxt.com/issues/325",0.7358505,{"description":2948,"labels":2949,"number":2950,"owner":2868,"repository":2911,"state":2912,"title":2951,"updated_at":2952,"url":2953,"score":2954},"With a dropdown `heroicons-outline:dots-vertical` I can:\n\n- [ ] Rename\n- [ ] Revert\n- [ ] Delete",[],198,"Media images actions","2023-02-15T12:31:53Z","https://github.com/nuxt/nuxt.com/issues/198",0.73798627,{"description":2956,"labels":2957,"number":2959,"owner":2868,"repository":2911,"state":2912,"title":2960,"updated_at":2961,"url":2962,"score":2963},"Blocked by #293 \n\nMedia files \"data\" (content and dimensions) are stored via `useState` and never cleared.\nEnsure that behavior does not cause issues or fix it, in case we save a media file \"data\" for a specific path then later a completely different file with the same path exists.\n\nUsecase:\n`public/foo.png` exists => fetch and save data for this path.\nrename `public/foo.png` to `public/bar.png` => fetch and save data for this path.\ncreate a new file `public/foo.png` => this new file should have old data and will not refresh it",[2958],{"name":2879,"color":2909},311,"Manage `medias` when doing actions on files","2023-02-15T12:32:07Z","https://github.com/nuxt/nuxt.com/issues/311",0.75892925,{"description":2965,"labels":2966,"number":2959,"owner":2868,"repository":2888,"state":2912,"title":2967,"updated_at":2968,"url":2969,"score":2963},"### Environment\n\nhttps://github.com/Rigo-m/nuxt-vitest-error-test\n\n### Reproduction\n\nhttps://github.com/Rigo-m/nuxt-vitest-error-test\n\n### Describe the bug\n\nRunning pnpm i && pnpm --filter global test gives the following error: \r\n```\r\nError: [@vue/compiler-sfc] No fs option provided to `compileScript` in non-Node environment. File system access is required for resolving imported types.\r\n\r\n/Users/rigo/Projects/nuxt-test-utils-test/packages/layer/components/Test.vue\r\n5 | \u003Cscript setup lang=\"ts\">\r\n6 | import type { TestProps } from \"./test.props\";\r\n7 | defineProps\u003CTestProps>();\r\n | ^^^^^^^^^\r\n8 | \u003C/script>\r\n```\n\n### Additional context\n\nRemoving vitest.config.ts make e2e tests works, but (obviously) kills unit tests using nuxt vitest environment\n\n### Logs\n\n_No response_",[],"nuxt-vitest + nuxt test utils not working properly together","2023-12-02T00:18:09Z","https://github.com/nuxt/test-utils/issues/311",["Reactive",2971],{},["Set"],["ShallowReactive",2974],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7vJECWtrGyXXN4Zc_vTJc_WpKWkZjHWN1SjKvgIACcI":-1},"/nuxt/scripts/347"]