\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.7766421,{"description":3154,"labels":3155,"number":3165,"owner":3146,"repository":3166,"state":3148,"title":3167,"updated_at":3168,"url":3169,"score":3170},"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.",[3156,3159,3162],{"name":3157,"color":3158},"enhancement","a2eeef",{"name":3160,"color":3161},"good first issue","7057ff",{"name":3163,"color":3164},"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.7819675,{"description":3172,"labels":3173,"number":3177,"owner":3146,"repository":3178,"state":3148,"title":3179,"updated_at":3180,"url":3181,"score":3182},"### 📚 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_",[3174],{"name":3175,"color":3176},"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":3184,"labels":3185,"number":3187,"owner":3146,"repository":3178,"state":3188,"title":3189,"updated_at":3190,"url":3191,"score":3192},"### 🆒 Your use case\n\nWhen using the Nuxt Scripts module to bundle global scripts on Vercel, I occasionally encounter a build error caused by a fetch operation timing out. This issue is likely due to the default fetch timeout being too short for certain network conditions. Introducing a configurable `bundle` object would enable developers to customize fetch behavior and bundling, thereby reducing the likelihood of timeouts and other fetch-related errors.\n\n### 🆕 The solution you'd like\n\nUpdate the `bundle` property to be an object instead of a boolean. If the `bundle` object is defined, bundling is enabled. The object should include options for retries, retry delays, and fetch timeouts, as shown below. More options can be considered; however, the following ones are the most important I could think of:\n\n```ts\nscripts: {\n bundle: {\n fetchRetries: 3, // Specifies the number of retry attempts for failed fetches.\n fetchRetryDelay: 2000, // Specifies the delay (in milliseconds) between retry attempts.\n fetchTimeout: 30000 // Configures the maximum time (in milliseconds) allowed for each fetch attempt.\n }\n}\n```\n\nThis approach keeps the configuration modular and allows developers to easily enable or disable bundling by defining or omitting the `bundle` object.\n\n### 🔍 Alternatives you've considered\n\n_No response_\n\n### ℹ️ Additional info\n\nThe error seems to stem from the undici library's internalConnectMultipleTimeout function during resource fetching. My `nuxt.config.ts` and the build logs are attached below:\n\n- [nuxt.config.ts](https://github.com/JonathanXDR/Application-Website-Frontend/blob/84b3b3c5f777235931d8f019dd0b8c4b610dbbbb/nuxt.config.ts#L178C3-L196C5)\n\n- #### Build Logs\n \u003Cimg width=\"1077\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b5dcc199-de86-4cde-a927-3884ae580aae\" />",[3186],{"name":3157,"color":3158},347,"closed","Add configuration options for fetch timeout, fetch retries and retry delays","2025-02-07T02:36:55Z","https://github.com/nuxt/scripts/issues/347",0.4476654,{"description":3194,"labels":3195,"number":3201,"owner":3146,"repository":3202,"state":3188,"title":3203,"updated_at":3204,"url":3205,"score":3206},"- [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",[3196,3198],{"name":3157,"color":3197},"1ad6ff",{"name":3199,"color":3200},"responsive","1cd1c6",642,"nuxt.com","[Project] Content + Media responsive files aside","2023-02-15T12:32:40Z","https://github.com/nuxt/nuxt.com/issues/642",0.70917255,{"description":3208,"labels":3209,"number":3201,"owner":3146,"repository":3166,"state":3188,"title":3213,"updated_at":3214,"url":3215,"score":3206},"### 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_",[3210],{"name":3211,"color":3212},"pending triage","5D08F5","Unable to install main branch","2023-12-12T13:29:02Z","https://github.com/nuxt/test-utils/issues/642",{"description":3217,"labels":3218,"number":3220,"owner":3146,"repository":3202,"state":3188,"title":3221,"updated_at":3222,"url":3223,"score":3224},"As for branches, we'll need to reload the cache.",[3219],{"name":3157,"color":3197},325,"Refresh files action in files modal","2023-02-15T12:32:08Z","https://github.com/nuxt/nuxt.com/issues/325",0.7358505,{"description":3226,"labels":3227,"number":3228,"owner":3146,"repository":3202,"state":3188,"title":3229,"updated_at":3230,"url":3231,"score":3232},"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":3234,"labels":3235,"number":3237,"owner":3146,"repository":3202,"state":3188,"title":3238,"updated_at":3239,"url":3240,"score":3241},"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",[3236],{"name":3157,"color":3197},311,"Manage `medias` when doing actions on files","2023-02-15T12:32:07Z","https://github.com/nuxt/nuxt.com/issues/311",0.75892925,{"description":3243,"labels":3244,"number":3237,"owner":3146,"repository":3166,"state":3188,"title":3245,"updated_at":3246,"url":3247,"score":3241},"### 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",3249],{},["Set"],["ShallowReactive",3252],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f50GKnd_1GkVDSXrL4XuQRIup1ZIvbrUM-FAlL_bVpfQ":-1},"/nuxt/nuxt.com/347"]