, found can not load this icon\n\n### Description\n\nEarlier versions could inject custom ICONS in this way and display them correctly using I-BV-heart, but this seems to be invalid in the new version. i have seen an interrupt change in the version that mentions migrating from @egoist/tailwindcss-icons to @nuxt/icon library. So can you provide a description of how I should configure the migration in the new version of this scenario\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2971],{"name":2919,"color":2920},3612,"How to inject customer icon","2025-03-20T15:39:12Z","https://github.com/nuxt/ui/issues/3612",0.7277892,{"description":2978,"labels":2979,"number":2986,"owner":2909,"repository":2928,"state":2910,"title":2987,"updated_at":2988,"url":2989,"score":2990},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: modules, compatibilityDate, devtools, css, ui, devServer, future, telemetry, hooks, eslint\n- Runtime Modules: @nuxt/eslint@0.6.2, @nuxt/ui-pro@3.0.1, nuxt-jsonld@2.1.0, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt v3.16.1\nui-pro v3.0.1\n\n### Reproduction\n\nWhen I add the following to my nuxt.config.ts:\n\n```ts\n{\n ui: {\n colorMode: false\n }\n}\n```\n\n...then `npx nuxi typecheck` fails with 8 errors.\n\n```\n[...snip]\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n18 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\n\nFound 8 errors in 8 files.\n\nErrors Files\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSwitch.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/content/ContentSearch.vue:89\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/DashboardSearch.vue:57\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10\n\n ERROR Process exited with non-zero status (2)\n```\n\n### Description\n\nI think that there probably needs to be a stub export set up in all cases? Or these files should not be gathered by the typechecking script?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2980,2981,2982,2985],{"name":2919,"color":2920},{"name":2922,"color":2923},{"name":2983,"color":2984},"pro","5BD3CB",{"name":2925,"color":2926},3657,"Setting ui.colorMode = false breaks nuxi typecheck","2025-03-27T20:54:57Z","https://github.com/nuxt/ui/issues/3657",0.7317073,{"description":2992,"labels":2993,"number":2994,"owner":2909,"repository":2995,"state":2910,"title":2996,"updated_at":2997,"url":2998,"score":2999},"@harlan-zw hi!\r\n\r\nI may have missed it somewhere, although I've gone through the documentation completely.\r\nCan you please tell me if it is possible to add two or more GTM containers?\r\nIf so, how do I use them?\r\n\r\nIn brief - I need to use different gtm-id on different url's. And the GTM script should be loaded immediately, by default",[],154,"scripts","Two or more GTM containers","2024-08-07T02:22:06Z","https://github.com/nuxt/scripts/issues/154",0.7364151,{"description":3001,"labels":3002,"number":3007,"owner":2909,"repository":2909,"state":2910,"title":3008,"updated_at":3009,"url":3010,"score":3011},"### Version\n\n[v2.8.1](https://github.com/nuxt.js/releases/tag/v2.8.1)\n\n### Reproduction link\n\n[http://empy](http://empy)\n\n### Steps to reproduce\n\n1. create new project with minimum setup (no add any modules / packages) via `create-nuxt-app`.\n2. create new folder at root project named `serverMiddleware`.\n3. create new file inside `serverMiddleware` folder, named `test.middleware.js`. add content (see bottom):\n4. open `nuxt.config.js`. add into `watch` property : `watch: ['serverMiddleware/test.middleware.js']`. Note: `config.watch` not `config.build.watch`\n5. run `yarn dev` to host dev mode, open site in browser and f5 several times. We will see in terminal the console `~this xxx` message.\n6. open `test.middleware.js` and edit string from `~ this` to `~ this edited`. save file. We will see in terminal the server auto restarted.\n7. After restart done, refresh brower and see message changed. Repeat step 6, 7 to make sure server restart no issue.\n8. turn off process (ctrl + c). then open `nuxt.config.js`, edit watch file string from `serverMiddleware/test.middleware.js` to `serverMiddleware/*.js`.\n9. start server by `yarn dev`. refresh browser to see message show on.\n10. repeat step 6, 7. The watcher will failed with trap 6 nodejs report at second restart.\n\n### test.middleware.js\n```js\nexport default {\n handler: function(req, res, next) {\n // req is the Node.js http request object\n console.log('~ this ', req.path)\n\n // res is the Node.js http response object\n\n // next is a function to call to invoke the next middleware\n // Don't forget to call next at the end if your middleware is not an endpoint!\n next()\n }\n}\n```\n\n### What is expected ?\n\nconfig.watch with wildcard should work no issue.\n\n### What is actually happening?\n\nconfig.watch failed when restart second times if watch string contains wildcard syntaxs\n\n### Additional comments?\n\nPs: also i found that serverMiddleware will cache somewhere outside nuxt processing if in `config.serverMiddlware` property we use string file path.\nIf we require middleware file use `require()` inside `nuxt.config.js` then import direct to `config.serverMiddleware` and add file path to `config.watch` then project will listen and restart correctly.\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c9642\">#c9642\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3003,3005,3006],{"name":3004,"color":2926},"stale",{"name":2958,"color":2959},{"name":2961,"color":2962},6232,"`config.watch` failed at second restart if use wildcard","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6232",0.7373673,{"description":3013,"labels":3014,"number":3018,"owner":2909,"repository":3019,"state":2910,"title":3020,"updated_at":3021,"url":3022,"score":3023},"## Steps to reproduce\r\n\r\nRun tests including the JSDOM ones: `pnpm test`\r\nThe following tests are failing:\r\n```\r\n 脳 can use $fetch\r\n 脳 can mock fetch requests 5014ms\r\n```\r\n\r\n## Triage\r\n\r\nThis seems to be a compatibility issue coming from the `Headers` implementation in `node-fetch`. This is discussed further [here](https://github.com/node-fetch/node-fetch/issues/1119).\r\n\r\nJSDOM uses the package [whatwg-url](https://github.com/jsdom/whatwg-url) which has a standard compliant implementation of `URLSearchParams`. When `node-fetch` (incorrectly) implements `Headers` using `URLSearchParams` from `whatwg-url` we get the error seen in the tests.\r\n\r\nI'm assuming Happy-DOM has an implementaiton of `URLSearchParams` that is less strict, and thus we do not get these errors there.\r\n\r\nIt also seems like [this line](https://github.com/danielroe/nuxt-vitest/blob/main/packages/vitest-environment-nuxt/src/index.ts#L64) is not working as intended since `globalThis.fetch` is `undefined` even in Node 18. Probably there is some isolation going on in Vitest that is preventing us from accessing the Node global.\r\n",[3015],{"name":3016,"color":3017},"vitest-environment","b60205",530,"test-utils","fetch does not work when using JSDOM","2023-12-02T00:32:10Z","https://github.com/nuxt/test-utils/issues/530",0.73777604,["Reactive",3025],{},["Set"],["ShallowReactive",3028],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQ3hyScp4vkvqJHKbcr1BBnj5WEksMmk_hJQUc0EAKg4":-1},"/nuxt/nuxt.com/1179"]