",[3183,3184,3185],{"name":3154,"color":3155},{"name":3174,"color":3175},{"name":3157,"color":3158},4084,"Incorrect display of \"Today\" in the calendar","2025-05-06T15:36:48Z","https://github.com/nuxt/ui/issues/4084",0.7015937,{"description":3192,"labels":3193,"number":3199,"owner":3143,"repository":3143,"state":3161,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.17.0`\n- Nuxt Version: `4.0.3`\n- CLI Version: `3.27.0`\n- Nitro Version: `2.12.4`\n- Package Manager: `pnpm@10.14.0`\n- Builder: `-`\n- User Config: `modules`, `pages`, `dir`, `vite`, `typescript`\n- Runtime Modules: `()`, `()`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-wzqq2xfw?file=app/app.vue\n\n### Describe the bug\n\nI noticed that after building Nuxt, the `%` unit in CSS gets stripped from all values that are `0`, which causes the `linear()` timing function to break, because it always expects a percentage on the right side.\n\n```css\n.example {\n transition-timing-function: linear(0 0%, 1 100%);\n}\n```\n\n\u003Cimg width=\"341\" height=\"46\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4c4773e8-25c4-4c88-ab33-9697c9d685a5\" />\n\n### Steps to reproduce\n1. run `pnpm build`\n2. run `pnpm preview`\n3. inspect the CSS of the `Example` div\n\n### Additional context\n\nMight not be a Nuxt bug, but I wasn't able to reproduce it in plain Vue: https://stackblitz.com/edit/vitejs-vite-u8bwhrqx?file=src/App.vue&terminal=dev\n\n### Logs\n\n```shell-script\n\n```",[3194,3196],{"name":3140,"color":3195},"E99695",{"name":3197,"color":3198},"upstream","E8A36D",33014,"CSS unit stripped after build in the `linear()` timing function causes it to break","2025-08-20T11:04:16Z","https://github.com/nuxt/nuxt/issues/33014",0.71365577,{"labels":3205,"number":3210,"owner":3143,"repository":3143,"state":3161,"title":3211,"updated_at":3212,"url":3213,"score":3214},[3206,3207],{"name":3140,"color":3195},{"name":3208,"color":3209},"2.x","d4c5f9",7915,"Nuxt memory leak universal mode","2023-01-22T15:36:07Z","https://github.com/nuxt/nuxt/issues/7915",0.71956897,{"description":3216,"labels":3217,"number":3222,"owner":3143,"repository":3143,"state":3161,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.0\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: telemetry\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/unruffled-jang-8f7ywm\r\n\r\n`yes` should be black, not red.\r\n\r\n\r\n\n\n### Describe the bug\n\nA client side plugin which modifies `state` variables will cause a rendering mistake.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3218,3221],{"name":3219,"color":3220},"3.x","29bc7f",{"name":3140,"color":3195},24409,"Rendering incorrect content when client plugin modifies state variables","2023-11-28T09:47:11Z","https://github.com/nuxt/nuxt/issues/24409",0.72035205,{"description":3228,"labels":3229,"number":3238,"owner":3143,"repository":3160,"state":3161,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: pnpm@10.9.0\n- Builder: -\n- User Config: modules, colorMode, image, content, plausible, devtools, hub, css, mdc, nitro, runtimeConfig, routeRules, future, compatibilityDate, eslint\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/image@1.10.0, @nuxt/ui-pro@3.1.0, @nuxt/content@3.5.1, @nuxthub/core@0.8.25, @nuxtjs/plausible@1.2.0, @vueuse/nuxt@13.1.0, nuxt-og-image@5.1.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\n1. Open [saas-template.nuxt.dev](https://saas-template.nuxt.dev/) in Safari on macOS 18.4.\n2. Scroll to the Testimonials section.\n3. Observe that after a line break in the grid, the first card in each new row is not rendered.\n4. Open Safari’s developer tools and disable the first CSS rule:\n```\n:is(.*:will-change-transform>*) {\n will-change: transform;\n}\n```\n5. Observe that the missing cards now appear, but borders render incorrectly.\n\n\n### Description\n\nOn Safari for macOS (Version 18.4 – 20621.1.15.11.10), using @nuxt/ui components in a responsive grid layout causes elements to disappear after a line break. Specifically, the first item in each new row is not rendered when will-change: transform is applied.\n\n**🔍 Context**\nThe issue is reproducible on your official SaaS template: [saas-template.nuxt.dev](https://saas-template.nuxt.dev/), in the testimonial section. This section uses only @nuxt/ui components – no @nuxt/ui-pro components are involved. The relevant code lives in [/app/pages/index.vue](https://github.com/nuxt-ui-pro/saas/blob/main/app/pages/index.vue), lines 58–80.\n\n**📍 Suspected Source**\nIn Safari, the following rule seems to break the layout:\n\n```\n:is(.*:will-change-transform>*) {\n will-change: transform;\n}\n```\nDisabling this rule in Safari's dev tools makes the hidden items visible again. However, doing so causes border-top rendering to break.\n\n\n**📸 Screenshots**\nIssue (first items not rendered):\n\n\nAfter disabling will-change (cards reappear):\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3230,3231,3234,3235],{"name":3154,"color":3155},{"name":3232,"color":3233},"duplicate","cfd3d7",{"name":3174,"color":3175},{"name":3236,"color":3237},"pro","5BD3CB",4026,"Safari Bug: Grid layout issues with `will-change: transform`","2025-04-30T13:51:05Z","https://github.com/nuxt/ui/issues/4026",0.72052103,{"labels":3244,"number":3247,"owner":3143,"repository":3143,"state":3161,"title":3248,"updated_at":3249,"url":3250,"score":3251},[3245,3246],{"name":3140,"color":3195},{"name":3208,"color":3209},7943,"Modern build is bigger with less browser requirements","2023-01-22T15:36:08Z","https://github.com/nuxt/nuxt/issues/7943",0.7221687,{"description":3253,"labels":3254,"number":3259,"owner":3143,"repository":3143,"state":3161,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.9.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.12.0\r\n- User Config: devtools, modules, css, sanity, image, components\r\n- Runtime Modules: @vueuse/nuxt@10.7.2, @vueuse/motion/nuxt@2.0.0, @nuxtjs/sanity@1.8.3, @unocss/nuxt@0.58.3, @pinia/nuxt@0.5.1, @nuxt/image@1.2.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-mz42kv\r\n\r\nGo to the follow reproduction, and manually refresh the web container. The page should briefly be unstyled. \n\n### Describe the bug\n\nAfter upgrading to Nuxt `3.9.2` this morning, I notice that all my pages and components become briefly unstyled when my local environment is initially loaded or a page manually refreshed. This happens with Unocss, the styling library I am using, but it may also be happening with other styling libraries. \n\n### Additional context\n\nI checked the Unocss issues, and no issues have been reported. This is likely not a Unocss bug (was working fine yesterday with Nuxt `3.9.1`)\n\n### Logs\n\n_No response_",[3255,3256],{"name":3219,"color":3220},{"name":3257,"color":3258},"❗ p4-important","D93F0B",25240,"Nuxt 3.9.2: Unstyled pages rendered briefly with Unocss","2024-01-17T10:00:45Z","https://github.com/nuxt/nuxt/issues/25240",0.7235581,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbNHyE4l4AlpiX3JS5-UvPLKCU2DAN9W38eQrBsLFCqg":-1},"/nuxt/ui/4794"]