\n \u003C/template>\n \u003Ctemplate #increment>\n \u003CUButton\n :loading=\"loadingInc\"\n variant=\"link\"\n icon=\"i-lucide-plus\"\n @click=\"loadingInc = true\"\n :ui=\"{\n base: 'text-gray-500 hover:text-[var(--ui-color-primary-500)] disabled:text-gray-500 cursor-pointer',\n }\"\n />\n \u003C/template>\n \u003C/UInputNumber>\n````\n\nbest,\ngregor\n\n### Additional context\n\n_No response_",[1984,1987,1990],{"name":1985,"color":1986},"enhancement","a2eeef",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"triage","ffffff",3159,"nuxt","ui","open","option to disable on press behaviour for increment/decrement for inputNumber component","2025-01-27T08:00:26Z","https://github.com/nuxt/ui/issues/3159",0.7892757,{"description":2002,"labels":2003,"number":2008,"owner":1994,"repository":2009,"state":1996,"title":2010,"updated_at":2011,"url":2012,"score":2013},"### Describe the feature\n\nI have a project where I've written multiple test files, each with their own `setup()` inside the top `describe()`\r\n\r\n```ts\r\ndescribe('/api/pen', async () => {\r\n await setup(setupConfig())\r\n...\r\n```\r\n\r\nWhen I run these tests it creates a nuxt instance for each test file, demonstrated here: https://github.com/fumeapp/bio/actions/runs/10505024117/job/29101731333#step:12:48\r\n\r\nI'm not sure if I have this setup incorrectly, or maybe if there was a way to have all test files share the same nuxt instance?\r\n\r\nP.S. I am working on a potential GH action version that will run nuxt in the background and allow a possible setup({host: ...}) version, if i get this working i'll share it.\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2004,2005],{"name":1985,"color":1986},{"name":2006,"color":2007},"pending triage","5D08F5",923,"test-utils","Ability to avoid a new nuxt instance for each test file","2024-08-22T09:25:17Z","https://github.com/nuxt/test-utils/issues/923",0.79264075,{"description":2015,"labels":2016,"number":2017,"owner":1994,"repository":2018,"state":2019,"title":2020,"updated_at":2021,"url":2022,"score":2023},"https://nuxt.com/docs/guide/directory-structure/nuxt-config\r\n\r\n",[],1555,"nuxt.com","closed","[question] Is this a typo?","2024-04-19T10:30:04Z","https://github.com/nuxt/nuxt.com/issues/1555",0.6824161,{"description":2025,"labels":2026,"number":2035,"owner":1994,"repository":1994,"state":2019,"title":2036,"updated_at":2037,"url":2038,"score":2039},"### Environment\n\n-\n\n### Reproduction\n\nhttps://nuxt.com/modules/tailwindcss\r\nhttps://nuxt.com/modules/nuxt-viewport\n\n### Describe the bug\n\nUsing the light theme we get code highlighting bug\r\n\u003Cimg width=\"1048\" alt=\"image\" src=\"https://user-images.githubusercontent.com/24970784/202643486-d93875f9-5281-4b09-9ac0-f9c964502058.png\">\r\n\u003Cimg width=\"1046\" alt=\"image\" src=\"https://user-images.githubusercontent.com/24970784/202643580-8d1c222f-3c4c-456a-b00a-a9746e1bd92e.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2027,2030,2033],{"name":2028,"color":2029},"documentation","5319e7",{"name":2031,"color":2032},"3.x","29bc7f",{"name":2006,"color":2034},"E99695",15531,"docs: markdown in modules with light theme are broken","2023-01-19T17:53:18Z","https://github.com/nuxt/nuxt/issues/15531",0.75027984,{"description":2041,"labels":2042,"number":2045,"owner":1994,"repository":1994,"state":2019,"title":2046,"updated_at":2047,"url":2048,"score":2049},"Hi,\r\n\r\nI noticed that the colorscheme of the code block in the documents of modules doesn't display well in light mode.\r\n\r\nFor example, in [@nuxt/tailwindcss](https://nuxt.com/modules/tailwindcss),\r\n\r\nThe color of the code is the same as the background, for example:\r\n\r\nIn light mode, I can't see any code but comments\r\n\r\n\r\nHowever, in dark mode, it works well\r\n\r\n\r\nThe braces in the code block have a similar issue as well, \r\n\r\nIn light mode, all the braces disappear:\r\n\r\n\r\nCompared with dark mode:\r\n\r\n",[2043,2044],{"name":2028,"color":2029},{"name":2031,"color":2032},15501,"Colorscheme of code blocks in light mode seems unclear","2023-02-15T13:09:14Z","https://github.com/nuxt/nuxt/issues/15501",0.7553443,{"description":2051,"labels":2052,"number":2055,"owner":1994,"repository":2018,"state":2019,"title":2056,"updated_at":2057,"url":2058,"score":2059},"Dark mode:\n- Apollo\n- Inkline\n- Lodash\n- purgecss\n- umami\n- unocss\n- xstate",[2053],{"name":1985,"color":2054},"1ad6ff",1002,"Modules: change logos in dark mode ? ","2023-10-10T14:45:27Z","https://github.com/nuxt/nuxt.com/issues/1002",0.7630304,{"description":2061,"labels":2062,"number":2067,"owner":1994,"repository":2009,"state":2019,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### Environment\r\n\r\nN/A\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nsetup fails\r\n\r\n### Additional context\r\n\r\ncc: @tobiasdiez \r\n\r\nHere are the lines\r\n\r\nhttps://github.com/nuxt/test-utils/blob/86d09da23a2d7ba6b0f3dcf2e9ca8c21655a5218/src/core/server.ts#L17-L71\r\n\r\noffending line for me was 57, but could easily be any other lines\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d\r\n\r\nis the offending commit \r\n\r\nspecifically this change\r\n\r\nhttps://github.com/nuxt/test-utils/commit/c4df41db447afe6101df10fbe763b198b12da86d#diff-84e9c1e393b43cee97ce99909a2db3a09bf9a2435daa2066b01a838e206edec3\r\n\r\n### Logs\r\n\r\n```shell-script\r\nN/A\r\n```\r\n",[2063,2066],{"name":2064,"color":2065},"bug","d73a4a",{"name":2006,"color":2007},918,"`ctx.nuxt` does not exist when `build: false` in setup","2024-12-05T14:26:41Z","https://github.com/nuxt/test-utils/issues/918",0.76598585,{"description":2073,"labels":2074,"number":2077,"owner":1994,"repository":1995,"state":2019,"title":2078,"updated_at":2079,"url":2080,"score":2081},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: -\n- CLI Version: 3.21.1\n- Nitro Version: -\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.12\n\n### Reproduction\n\nhttps://github.com/nuxt/starter/tree/ui3\n\n### Description\n\nTested both with\n1. the official [nuxt ui v3 starter template](https://github.com/nuxt/starter/tree/ui3)\n2. Following the manual installation steps outlined in https://ui3.nuxt.dev/getting-started/installation/nuxt#use-our-nuxt-starter\n\nAfter a fresh install of the nuxt ui3 starter project (cd7e386) as instructed by the [nuxt documentation](https://ui3.nuxt.dev/getting-started/installation/nuxt#use-our-nuxt-starter), spinning up the dev-server yields errors, rendering the project unusable. Tried with node 20 and 22. Both times, the following error appears:\n\n```\n ERROR Pre-transform error: [@vue/compiler-sfc] Failed to resolve extends base type. 2:44:13 PM\nIf this previously worked in 3.2, you can instruct the compiler to ignore this extend by adding /* @vue-ignore */ before it, for example:\n\ninterface Props extends /* @vue-ignore */ Base {}\n\nNote: both in 3.2 or with the ignore, the properties in the base type are treated as fallthrough attrs at runtime.\n\n/Users/\u003Csnip>/node_modules/@nuxt/ui/dist/runtime/components/Button.vue\n63 | \n64 | const loadingAutoState = ref(false)\n65 | const formLoading = inject\u003CRef\u003Cboolean> | undefined>(formLoadingInjectionKey, undefined)\n | ^^^^^^^^^^^^^^^^^^^^^^^^^^\n66 | \n | ^\n67 | async function onClickWrapper(event: MouseEvent) {\n | ^^^^^\n Plugin: vite:vue\n File: /Users/\u003Csnip>/node_modules/@nuxt/ui/dist/runtime/components/Button.vue\n```\n\nThe result is a 500er page when visiting localhost in the web browser.\n\nI am aware there were other issues with this error message suggesting to install typescript as a devDependency. I believe this is not the solution here because typescript is already a devDependency in the ui3 starter template. Another suggestion was to add a tsconfig.json. This also already exists in the starter template.\n\nFinally, other people are experiencing the same issue, with multiple people posting the same error message in the official Nuxt Discord.\n\n### Additional context\n\nDiscord questions with the same issue\nhttps://discord.com/channels/473401852243869706/1304812159540396055\nhttps://discord.com/channels/473401852243869706/1334142349026267187\n\n\n### Logs\n\n```shell-script\n\n```",[2075,2076],{"name":2064,"color":2065},{"name":1988,"color":1989},3262,"ui v3 can not be started","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3262",0.7660444,{"description":2083,"labels":2084,"number":2087,"owner":1994,"repository":2018,"state":2019,"title":2088,"updated_at":2089,"url":2090,"score":2091},"",[2085],{"name":2064,"color":2086},"ff281a",124,"Milkdown editor only works in dark mode","2023-06-06T12:14:49Z","https://github.com/nuxt/nuxt.com/issues/124",0.7748106,{"description":2093,"labels":2094,"number":2096,"owner":1994,"repository":2018,"state":2019,"title":2097,"updated_at":2098,"url":2099,"score":2100},"> As of right now, the `ui` module does not support overriding the gray color",[2095],{"name":1985,"color":2054},486,"Dark mode with custom gray palette","2022-05-18T09:03:31Z","https://github.com/nuxt/nuxt.com/issues/486",0.7773884,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"EOUDDbtU1PJIOAxNfA0E9AKkp2y0IM4jhJ-w1nvVjGw":-1},"/nuxt/ui/3146"]