",[2867,2870],{"name":2868,"color":2869},"question","d876e3",{"name":2871,"color":2872},"v3","49DCB8",3947,"nuxt","ui","open","Unexpected drawer behavior when dragging content area (jumpy collapse & horizontal scroll flickering)","2025-04-21T09:17:02Z","https://github.com/nuxt/ui/issues/3947",0.70798224,{"description":2882,"labels":2883,"number":2887,"owner":2874,"repository":2874,"state":2876,"title":2888,"updated_at":2889,"url":2890,"score":2891},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: modules, $development, devtools, app, css, runtimeConfig, routeRules, future, compatibilityDate, vite, postcss, eslint, i18n, image, prismic, scripts\n- Runtime Modules: @nuxt/eslint@1.3.1, @nuxtjs/prismic@4.1.0, @nuxt/fonts@0.11.2, @nuxtjs/i18n@9.5.4, @nuxt/image@1.10.0, @vueuse/nuxt@13.1.0, @hebilicious/vue-query-nuxt@0.3.0, @nuxt/scripts@0.11.6\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://github.com/capitalenumerique/interfaceqc\n\n### Describe the bug\n\nOn my homepage, I have some static and dynamic text.\nWhen I change locale, the static text is updated, but not the dynamic text.\nSeems like my `useAsyncData` is not triggered on locale change.\nThis ONLY happens on my homepage\n\nOn the Home page:\n\nNot working ⛔ \n\nThe website: https://interfaceqc.com/en\nThe repo: https://github.com/capitalenumerique/interfaceqc/blob/main/app/pages/index.vue\nThe query:\n```js\nconst { data: page } = await useAsyncData('index', () => {\n return prismic.client.getSingle('home', {\n graphQuery: `{ ...truncated... }`,\n lang: `${locale.value}-ca`,\n });\n});\n```\n\n### Additional context\n\nOn the FAQ page (or any other page):\n\nWorking ✅ \n\n### Logs\n\n```shell-script\n\n```",[2884],{"name":2885,"color":2886},"pending triage","E99695",32104,"useAsyncData with same key on two different pages does not refresh when switching pages","2025-05-17T18:30:55Z","https://github.com/nuxt/nuxt/issues/32104",0.71186125,{"description":2893,"labels":2894,"number":2902,"owner":2874,"repository":2875,"state":2876,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Environment\n\n- Ubuntu (WSL 2)\n- Package manager Bun\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n[Reproduction repository](https://github.com/sergiooak/vue-nuxtui-bun-type-import)\n\n\n### Description\n\nI found a weird bug while import types from @nuxt/ui using the syntax \"import { type ComponentProps} from @nuxt/ui\"\nIt took me a long time to pinpoint what was causing the bug. If i use this syntax, and do a fresh install, in my case, bun i && bun dev, I got this weird \"internal\" error from tailwind without point exactly where the error is.\n\nIf I clean the node_modules rewrite the import to \"import type {ComponentProps} from @nuxt/ui\" bun i && bun dev, the problem solves.\n\nI don't know if this is bun related or not, I am creating a minimal reproduction repo using npm and bun ASAP\n(I've just already created the issue in case someone find this bug in the meantime)\n\n### Additional context\n\nThe bug occurs only when using bun install with this specific import syntax for @nuxt/ui. Other imports using the same syntax work as expected. If bun install is run without this syntax, and the code is then adjusted accordingly, everything works fine. I only noticed this issue a few commits later due to this behavior\n\n### Logs\n\n```shell-script\n✘ [ERROR] Could not resolve \"../pkg\"\n\n node_modules/lightningcss/node/index.js:16:27:\n 16 │ module.exports = require(`../pkg`);\n ╵ ~~~~~~~~\n\n✘ [ERROR] No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-gnu/tailwindcss-oxide.linux-x64-gnu.node\n\n node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:190:38:\n 190 │ ...inding = require('@tailwindcss/oxide-linux-x64-gnu')\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n✘ [ERROR] No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-musl/tailwindcss-oxide.linux-x64-musl.node\n\n node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:177:38:\n 177 │ ...nding = require('@tailwindcss/oxide-linux-x64-musl')\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n/home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1476\n let error = new Error(text);\n ^\n\nError: Build failed with 3 errors:\nnode_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:177:38: ERROR: No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-musl/tailwindcss-oxide.linux-x64-musl.node\nnode_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/index.js:190:38: ERROR: No loader is configured for \".node\" files: node_modules/@nuxt/ui/node_modules/@tailwindcss/vite/node_modules/@tailwindcss/oxide/node_modules/@tailwindcss/oxide-linux-x64-gnu/tailwindcss-oxide.linux-x64-gnu.node\nnode_modules/lightningcss/node/index.js:16:27: ERROR: Could not resolve \"../pkg\"\n at failureErrorWithLog (/home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1476:15)\n at /home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:945:25\n at /home/sergiooak/gaio/gaio-web/node_modules/esbuild/lib/main.js:1354:9\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {\n errors: [Getter/Setter],\n warnings: [Getter/Setter]\n}\n```",[2895,2898,2899],{"name":2896,"color":2897},"bug","d73a4a",{"name":2871,"color":2872},{"name":2900,"color":2901},"triage","ffffff",3039,"Unexpected Bug with Tree-Shaking Type Imports in @nuxt/ui","2025-01-08T08:12:01Z","https://github.com/nuxt/ui/issues/3039",0.7154349,{"description":2908,"labels":2909,"number":2912,"owner":2874,"repository":2875,"state":2913,"title":2914,"updated_at":2915,"url":2916,"score":2917},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@10.6.3\n- Builder: -\n- User Config: compatibilityDate, devtools, future, experimental, modules, vite, css, typescript\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/test-utils@3.17.2, @nuxt/icon@1.11.0, @nuxt/ui@3.0.0\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu\n\n### Description\n\nThe InputMenu component only shows filtered items when opening it with a selected item. This is confusing, and differs from expected behavior. In its current state, the InputMenu would only be usable, if the user deletes the text in the field, which is not clear nor expected.\n\nExpected behavior: If one opens the select menu by clicking on the button, it shows all available values, with the currently selected value highlighted. Only when changing the text of the input field, it filters for the value entered.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2910,2911],{"name":2896,"color":2897},{"name":2871,"color":2872},3620,"closed","InputMenu shows only selected item when opening","2025-03-27T15:27:51Z","https://github.com/nuxt/ui/issues/3620",0.6369233,{"description":2919,"labels":2920,"number":2923,"owner":2874,"repository":2924,"state":2913,"title":2925,"updated_at":2926,"url":2927,"score":2928},"\n\nEx: https://dev.nuxt.com/community/repositories?organization=nuxtlabs&sortBy=stargazerCount",[2921],{"name":2896,"color":2922},"ff281a",552,"nuxt.com","Fix title in subnavbar in community section","2022-05-23T08:57:57Z","https://github.com/nuxt/nuxt.com/issues/552",0.6784374,{"description":2930,"labels":2931,"number":2923,"owner":2874,"repository":2938,"state":2913,"title":2939,"updated_at":2940,"url":2941,"score":2928},"`'NUXT_VITEST_DEV_TEST' is not recognized as an internal or external command, operable program or batch file.`\r\n\r\nYou may need to guide Windows developers to use WSL to build/run this project. 🤣 ",[2932,2935],{"name":2933,"color":2934},"documentation","0075ca",{"name":2936,"color":2937},"vitest-environment","b60205","test-utils","The development guide doesn't work on Windows","2023-12-02T00:17:07Z","https://github.com/nuxt/test-utils/issues/552",{"description":2943,"labels":2944,"number":2946,"owner":2874,"repository":2875,"state":2913,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### Description\n\nHi, using the UTable with Expanded feature is it possible to apply a style to the Expand column ??? I can see how to do this for columns I add but not the expanded column.\r\nAlso is it possible to change the default so the expanded is open by default? Or to change this in the script section?\r\n\r\nThanks I was unable to find answers in the docs.",[2945],{"name":2868,"color":2869},2244,"UTable Expandable questions?","2024-11-05T14:52:12Z","https://github.com/nuxt/ui/issues/2244",0.697283,{"description":2952,"labels":2953,"number":2954,"owner":2874,"repository":2955,"state":2913,"title":2956,"updated_at":2957,"url":2958,"score":2959},"Hello everyone!\r\n\r\nI've stumbled upon an error while writing tests for my components that use nuxt/icon, specifically:\r\n\r\n```\r\n[Vue warn]: Component \u003CNuxtIcon>: setup function returned a promise, but no \u003CSuspense> boundary was found in the parent component tree. A component with async setup() must be nested in a \u003CSuspense> in order to be rendered. \r\n```\r\n\r\nI've found in the docs of the [testutils](https://test-utils.vuejs.org/guide/advanced/async-suspense#Testing-asynchronous-setup) that you have to somehow wrap either `NuxtIcon` or `MyComponent` with `\u003CSuspense/>` and it is also unclear how to import `NuxtIcon` into the test file since we use `\u003CIcon/>` in the markup. Can you please show me how to write tests when using nuxt/icon ?\r\n\r\nI've created a reproduction setup, after installing all deps it will auto start the test and you will see the error.\r\n\r\n\r\nhttps://stackblitz.com/edit/nuxt-vitest-iocqwn\r\n\r\nBest regards",[],197,"icon","[QUESTION] How to write tests for components that use @nuxt/icon","2024-08-20T13:54:55Z","https://github.com/nuxt/icon/issues/197",0.6983776,{"description":2961,"labels":2962,"number":2965,"owner":2874,"repository":2875,"state":2913,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Description\n\nHi,\n\nI just tried upgrading to `v3` but I noticed that the `Meter` component is unfortunately missing in this version and the migration guide also doesn't mention anything regarding that component which currently prevents me from upgrading to v3 . [This issue](https://github.com/nuxt/ui/issues/1841) mentions that the component was still pending migration at some point in the beginning of 2024 besides some other components.\n\nIs the meter component still expected to arrive in v3 sometime soon? It would be quite unfortunate if this handy component would be stripped out of NuxtUI.\n",[2963,2964],{"name":2868,"color":2869},{"name":2871,"color":2872},3808,"Meter component missing in v3","2025-04-08T17:16:45Z","https://github.com/nuxt/ui/issues/3808",0.70824546,{"description":2971,"labels":2972,"number":2976,"owner":2874,"repository":2874,"state":2913,"title":2977,"updated_at":2978,"url":2979,"score":2980},"Can not figure out and find right solution. Everything not work.\r\n\r\nAfter authentication, i need to save data not only to Store and to localStorage, but also synchronize everything. That after page reload, user will be authed.\r\n\r\nnuxt.conf\r\n```\r\n plugins: [\r\n { src: '~/plugins/localStorage', ssr: false }\r\n ],\r\n\r\n```\r\nlocalStorage.js\r\n```\r\nimport createPersistedState from 'vuex-persistedstate'\r\n\r\nexport default ({store}) => {\r\n createPersistedState({\r\n storage: {\r\n getItem: key => localStorage.getItem(key),\r\n setItem: (key, value) => localStorage.setItem(key, value),\r\n removeItem: key => localStorage.removeItem(key)\r\n }\r\n })\r\n}\r\n\r\n```\r\n\r\nexample.vue component\r\n```\r\n import MyPlugin from '~/plugins/localStorage'\r\n\r\n export default {\r\n created() {\r\n console.log(MyPlugin);\r\n console.log(MyPlugin.local);\r\n console.log(MyPlugin.setting);\r\n// console.log(MyPlugin.storage.getItem('token'));\r\n// console.log(MyPlugin.getItem('token'));\r\n\r\n console.log(this.$store.local);\r\n console.log(this.$store.setting);\r\n },\r\n```\r\n\r\nNothing works\r\n`[HMR] connected\r\nform.vue?385a:89 ƒ (_ref) {\r\n var store = _ref.store;\r\n\r\n Object(__WEBPACK_IMPORTED_MODULE_0_vuex_persistedstate__[\"a\" /* default */])({\r\n storage: {\r\n getItem: function getItem(key) {\r\n …\r\nform.vue?385a:90 undefined\r\nform.vue?385a:91 undefined\r\nform.vue?385a:95 undefined\r\nform.vue?385a:96 undefined`\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c2625\">#c2625\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2973],{"name":2974,"color":2975},"2.x","d4c5f9",3031,"Persistedstate LocalStorage not work.","2023-01-18T16:09:51Z","https://github.com/nuxt/nuxt/issues/3031",0.7104014,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fw2T0PixsrsvW-o24oEdqJeo3fUNRlJNvtzDbZBN2EtM":-1},"/nuxt/nuxt.com/1504"]