\n до \u003CUInputNumber v-model=\"bill.to\" :min=\"bill.from\" :max=\"10000\" :step=\"calcStep(bill.to)\" variant=\"soft\" class=\"max-w-32\" />\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vT5m5gCX1Bk\n\nThe value changes when clicking outside the field, regardless of the `step` and `modelValue` state. The `step` parameter is also calculated incorrectly at the threshold of 1000.",[1995,1998,2001],{"name":1996,"color":1997},"bug","d73a4a",{"name":1999,"color":2000},"v3","49DCB8",{"name":2002,"color":2003},"triage","ffffff",2859,"ui","UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.7394578,{"description":2011,"labels":2012,"number":2019,"owner":1985,"repository":2005,"state":1987,"title":2020,"updated_at":2021,"url":2022,"score":2023},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nHi,\n\nI'm having issue correctly placing the popover for a `InputMenu` component. I have a bunch of pretty long options name, and I just want the popover to be placed underneath and stretching to display the option entirely. I used `placement: 'bottom-start'`, but I think it uses the down chevron as a reference point.\n\nI made [an example repo](https://stackblitz.com/edit/nuxt-ui-q5dqd7?file=app.vue) to show the expected behavior and the actual result.\n\nExpected: (rebuilt with a `Popover` component)\n\n\n\nActual: (`InputMenu` component)\n\n - Overflowing\n \n - Normal\n \n\nIs that a bug, or am I doing something wrong.",[2013,2016],{"name":2014,"color":2015},"question","d876e3",{"name":2017,"color":2018},"stale","ededed",2502,"Input menu popover placement","2025-02-14T01:58:48Z","https://github.com/nuxt/ui/issues/2502",0.7438517,{"description":2025,"labels":2026,"number":2027,"owner":1985,"repository":1986,"state":1987,"title":2028,"updated_at":2029,"url":2030,"score":2031},"\r\n\u003Cimg width=\"1229\" alt=\"image\" src=\"https://github.com/nuxt/nuxt.com/assets/73933669/a8b6473a-c737-4783-ad7f-148b07f0bf56\">\r\n\r\nhttps://github.com/nuxt/nuxt.com/assets/73933669/747e1528-e1b6-4c89-ae63-4afc0d74e471\r\n\r\n\r\nBrowser: Safari (i think this issue might be on every browser)\r\n\r\nHow to reproduce:\r\nSpam `cmd + r` if you're on windows `ctrl + r`.",[],1582,"Cannot load payload ~ A bug maybe","2024-05-15T07:13:12Z","https://github.com/nuxt/nuxt.com/issues/1582",0.746764,{"description":2033,"labels":2034,"number":2035,"owner":1985,"repository":2036,"state":1987,"title":2037,"updated_at":2038,"url":2039,"score":2040},"Coming from #443.\n\n- [ ] Return font file priority from `unifont`.\n- [ ] In Nuxt Fonts, skip preloading based on the priority.",[],508,"fonts","Should not preload fallback fonts","2025-02-18T08:02:34Z","https://github.com/nuxt/fonts/issues/508",0.7615843,{"description":2042,"labels":2043,"number":2047,"owner":1985,"repository":2048,"state":1987,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### 📚 What are you trying to do?\n\nWhen using the code, I get a center marker on the coordinates I want on the static map view, but as soon as the map gets active it disappears. The demo code in the docs, I don't see how it works since api is no longer worker. \n\n```\n\n\n\u003Cscript setup lang=\"ts\">\n import { ref } from \"vue\";\n import { useRuntimeConfig } from \"#app\";\n\n const config = useRuntimeConfig();\n const googleMapsApiKey = config.public.googleMapsApiKey;\n const leidenCoords = { lat: 52.160114, lng: 4.49701 }; // Coordinates for Leiden\n\n const mapOptions = {\n zoom: 10, // Set the initial zoom level\n center: { lat: 52.160114, lng: 4.49701 }, // Initial center position\n mapTypeControl: false, // Disables Map/Satellite option\n streetViewControl: false, // Disables Street View pegman\n fullscreenControl: false, // Disables fullscreen option\n scrollwheel: false, // Disables scroll wheel zoom\n styles: [\n {\n featureType: \"landscape\",\n stylers: [{ color: \"#f9ddc5\" }, { lightness: -7 }],\n },\n {\n featureType: \"road\",\n stylers: [{ color: \"#813033\" }, { lightness: 43 }],\n },\n {\n featureType: \"poi.business\",\n stylers: [{ color: \"#645c20\" }, { lightness: 38 }],\n },\n {\n featureType: \"water\",\n stylers: [\n { color: \"#1994bf\" },\n { saturation: -69 },\n { gamma: 0.99 },\n { lightness: 43 },\n ],\n },\n {\n featureType: \"road.local\",\n elementType: \"geometry.fill\",\n stylers: [\n { color: \"#f19f53\" },\n { weight: 1.3 },\n { visibility: \"on\" },\n { lightness: 16 },\n ],\n },\n { featureType: \"poi.business\" },\n {\n featureType: \"poi.park\",\n stylers: [{ color: \"#645c20\" }, { lightness: 39 }],\n },\n {\n featureType: \"poi.school\",\n stylers: [{ color: \"#a95521\" }, { lightness: 35 }],\n },\n {\n featureType: \"poi.medical\",\n elementType: \"geometry.fill\",\n stylers: [\n { color: \"#813033\" },\n { lightness: 38 },\n { visibility: \"off\" },\n ],\n },\n ],\n }; // Function to add the Leiden marker when map is ready\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"flex items-center justify-center w-full min-w-full\">\n \u003CScriptGoogleMaps\n :api-key=\"googleMapsApiKey\"\n :mapOptions=\"mapOptions\"\n class=\"h-64 rounded-lg min-w-full\"\n />\n \u003C/div>\n\u003C/template>\n\n\u003Cstyle scoped>\n /* Optional styling */\n\u003C/style>\n\n\u003Cstyle scoped>\n /* Ensure map has full width and fixed height */\n #map {\n width: 100%;\n height: 16rem; /* 64 Tailwind units */\n }\n\u003C/style>\n\n\n```\n\n\n\n\n### 🔍 What have you tried?\n\n_No response_\n\n### ℹ️ Additional context\n\n_No response_",[2044],{"name":2045,"color":2046},"help wanted","008672",314,"scripts","Centermarker disappears when loading active googlemap","2024-11-10T17:33:02Z","https://github.com/nuxt/scripts/issues/314",0.76529026,{"description":2054,"labels":2055,"number":2047,"owner":1985,"repository":2059,"state":1987,"title":2060,"updated_at":2061,"url":2062,"score":2052},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-framework-zehqm6\n\n### Describe the bug\n\nThe empty `await setup({})` in the tests takes ~4 seconds for every rerun in `watch` mode in the empty project.\r\nPlease, check the reproduction, try to run `npm test`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2056],{"name":2057,"color":2058},"enhancement","a2eeef","test-utils","The \"setup\" in the tests is very slow for every rerun","2024-12-03T16:02:16Z","https://github.com/nuxt/test-utils/issues/314",{"description":2064,"labels":2065,"number":2069,"owner":1985,"repository":2059,"state":2070,"title":2071,"updated_at":2072,"url":2073,"score":2074},"I'm getting the following errors\r\n\r\n```\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: Environment \"nuxt\" is not a valid environment. \r\n```\r\n\r\nthis happens on `vitest ` version > 0.34 \r\nno errors with vitest 0.33\r\n\r\n\r\n```\r\nimport { defineVitestConfig } from 'nuxt-vitest/config';\r\n\r\nexport default defineVitestConfig({\r\n test: {\r\n environment: 'nuxt',\r\n },\r\n});\r\n\r\n\r\n```",[2066],{"name":2067,"color":2068},"vitest-environment","b60205",520,"closed"," Vitest 0.34 error - Environment \"nuxt\" is not a valid environment","2023-12-02T00:37:17Z","https://github.com/nuxt/test-utils/issues/520",0.6978053,{"description":2076,"labels":2077,"number":2078,"owner":1985,"repository":1986,"state":2070,"title":2079,"updated_at":2080,"url":2081,"score":2082},"\r\n\r\n",[],1438,"[Support] Workshops & Trainings link directs to HTTP 404","2023-12-04T11:28:56Z","https://github.com/nuxt/nuxt.com/issues/1438",0.7201161,{"description":2084,"labels":2085,"number":2086,"owner":1985,"repository":2059,"state":2070,"title":2087,"updated_at":2088,"url":2089,"score":2090},"Originally reported by nuxt/test-utils#329, when having multiple `.test` files, jest runs them in parallel. If two depending on a single fixture and need build, this causes issues. Some options are:\r\n\r\n- Using run-in-band to disable parallel run\r\n- Using a lock-file so one test awaits on others during build\r\n- Using random build ids for `buildDir`\r\n- Using mfs (#49) for building in mem (considering all internals can support)\r\n\r\n",[],413,"fix: build conflict between multiple tests","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/413",0.7402355,["Reactive",2092],{},["Set"],["ShallowReactive",2095],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"bvLCLcRuP4r1UEGmz8ybRLu0DZ-ntSx_4ZqAx5Cuq8s":-1},"/nuxt/nuxt.com/1448"]