",[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.6171618,{"description":2882,"labels":2883,"number":2891,"owner":2874,"repository":2875,"state":2876,"title":2892,"updated_at":2893,"url":2894,"score":2895},"### 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```",[2884,2887,2888],{"name":2885,"color":2886},"bug","d73a4a",{"name":2871,"color":2872},{"name":2889,"color":2890},"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.6688806,{"description":2897,"labels":2898,"number":2901,"owner":2874,"repository":2875,"state":2902,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Description\n\nThe light mode defaults for Select are pretty good. Not as good for dark mode. How can I at least modify the background and text color of the popup list for dark mode? What is the recommended approach?\n\n\n",[2899,2900],{"name":2868,"color":2869},{"name":2871,"color":2872},3595,"closed","How can I improve the dark style of USelect","2025-03-18T20:19:24Z","https://github.com/nuxt/ui/issues/3595",0.6171704,{"description":2908,"labels":2909,"number":2911,"owner":2874,"repository":2912,"state":2902,"title":2913,"updated_at":2914,"url":2915,"score":2916},"Thought this issue was related to my project, but I was able to reproduce it, sounds weird but this font won't work on a production build - https://fonts.google.com/specimen/DM+Serif+Display\r\n\r\nI am using the font by mentioning it in my tailwind config \r\n\r\n```ts\r\nimport type { Config } from \"tailwindcss\";\r\n\r\nexport default \u003CPartial\u003CConfig>>{\r\n theme: {\r\n fontFamily: {\r\n sans: [\r\n \"DM Sans\",\r\n \"Avenir Next\",\r\n \"Roboto\",\r\n \"-apple-system\",\r\n \"BlinkMacSystemFont\",\r\n '\"Segoe UI\"',\r\n \"Ubuntu\",\r\n '\"Helvetica Neue\"',\r\n \"Arial\",\r\n '\"Noto Sans\"',\r\n \"sans-serif\",\r\n '\"Apple Color Emoji\"',\r\n '\"Segoe UI Emoji\"',\r\n '\"Segoe UI Symbol\"',\r\n '\"Noto Color Emoji\"',\r\n ],\r\n mono: [\r\n \"Cascadia Code\",\r\n \"ui-monospace\",\r\n \"SFMono-Regular\",\r\n \"Menlo\",\r\n \"Monaco\",\r\n \"Consolas\",\r\n \"Liberation Mono\",\r\n \"Courier New\",\r\n \"monospace\",\r\n ],\r\n display: [\"DM Serif Display\", \"Inter\", \"sans-serif\"],\r\n },\r\n },\r\n plugins: [require(\"@tailwindcss/typography\")],\r\n};\r\n```\r\n\r\nThe first font `DM Sans` is loads correctly, but the display font wont, throws a 404 in production.\r\n\r\nHere's a reproduction - https://github.com/fayazara/nuxt-font-repro\r\n\r\nDev environment screenshot \r\n\r\n\r\n\r\nProduction screenshot\r\n",[2910],{"name":2885,"color":2886},122,"fonts","This font won't work on production: DM Serif Display","2024-05-03T08:11:09Z","https://github.com/nuxt/fonts/issues/122",0.6365103,{"description":2918,"labels":2919,"number":2923,"owner":2874,"repository":2924,"state":2902,"title":2925,"updated_at":2926,"url":2927,"score":2928},"",[2920],{"name":2921,"color":2922},"enhancement","1ad6ff",576,"nuxt.com","Rename `/integrations` to `/modules`","2022-06-07T09:57:17Z","https://github.com/nuxt/nuxt.com/issues/576",0.6394559,{"description":2930,"labels":2931,"number":2923,"owner":2874,"repository":2935,"state":2902,"title":2936,"updated_at":2937,"url":2938,"score":2928},"I some unit tests, before using this setup I was able to set `process.client = false` or `process.server` and then in my test it would be set to false so I can ensure certain expectations e.g.\r\n\r\n```\r\ntest.todo('API Url set correctly for server-side requests', () => {\r\n let $cwa\r\n // todo: why can we not set the process vars in the test\r\n process.client = false\r\n\r\n $cwa = createCwa({ storeName })\r\n expect($cwa.apiUrl).toBe('https://api-url-not-set.com')\r\n\r\n $cwa = createCwa({ storeName, apiUrl: 'https://api-url', apiUrlBrowser: 'https://api-url-browser' })\r\n expect($cwa.apiUrl).toBe('https://api-url')\r\n\r\n $cwa = createCwa({ storeName, apiUrlBrowser: 'https://api-url-browser' })\r\n expect($cwa.apiUrl).toBe('https://api-url-browser')\r\n })\r\n```\r\n\r\nThese are just unit tests and I'm wondering why this does not work using this setup and if there's a better way to do this that is supported in my unit tests?",[2932],{"name":2933,"color":2934},"vitest-environment","b60205","test-utils","Simulating a server-side/client-side request by setting process.client or process.server","2023-12-02T00:37:11Z","https://github.com/nuxt/test-utils/issues/576",{"description":2940,"labels":2941,"number":2942,"owner":2874,"repository":2924,"state":2902,"title":2943,"updated_at":2944,"url":2945,"score":2946},"- [ ] Community profiles (doc & code contributors)\n- [ ] Login GitHub & Socials\n- [ ] Edit on Studio\n",[],1307,"Main features improvements","2023-07-10T12:41:54Z","https://github.com/nuxt/nuxt.com/issues/1307",0.6598586,{"description":2948,"labels":2949,"number":2950,"owner":2874,"repository":2912,"state":2902,"title":2951,"updated_at":2952,"url":2953,"score":2954},"When the weights are defined string arrays in the config, the fontshare provider would fail to match the correct weights because of the type mismatch.\r\n\r\n**My config**:\r\n```\r\nexport default defineNuxtConfig({\r\n modules: ['@nuxt/fonts', '@nuxtjs/tailwindcss', '@unocss/nuxt'],\r\n unocss: {\r\n disableNuxtInlineStyle: false,\r\n },\r\n fonts: {\r\n providers: {\r\n custom: '~/providers/custom'\r\n },\r\n families: [\r\n { name: 'Abel', provider: 'bunny' },\r\n { name: 'Satoshi', provider: 'fontshare' },\r\n { name: 'Kode Mono', provider: 'none' },\r\n { name: 'MyCustom', src: '/custom-font.woff2' },\r\n { name: 'CustomGlobal', global: true, src: '/font-global.woff2' },\r\n { name: 'Oswald', fallbacks: ['Times New Roman'] },\r\n ],\r\n defaults: {\r\n weights: ['400', '700'],\r\n fallbacks: {\r\n monospace: ['Tahoma']\r\n }\r\n }\r\n },\r\n})\r\n```",[],46,"Failure to match font weights for `fontshare` provider when the `weights` defined in the config is composed of strings.","2024-03-10T17:18:52Z","https://github.com/nuxt/fonts/issues/46",0.67191285,{"description":2956,"labels":2957,"number":2960,"owner":2874,"repository":2875,"state":2902,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### 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```",[2958,2959],{"name":2885,"color":2886},{"name":2871,"color":2872},3620,"InputMenu shows only selected item when opening","2025-03-27T15:27:51Z","https://github.com/nuxt/ui/issues/3620",0.68260324,{"description":2918,"labels":2966,"number":2971,"owner":2874,"repository":2924,"state":2902,"title":2972,"updated_at":2973,"url":2974,"score":2975},[2967,2968],{"name":2921,"color":2922},{"name":2969,"color":2970},"responsive","1cd1c6",807,"[Docs] Framework V3 improvements (mobile/tablet)","2023-02-15T12:30:59Z","https://github.com/nuxt/nuxt.com/issues/807",0.68285483,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgPMPErqfCFo9Ml5kh8vanR7VmathuNRv1yTGMBd7ln8":-1},"/nuxt/nuxt.com/597"]