\n\n\u003Cimg width=\"712\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0a9f273f-cb27-4824-ac2f-6497980294ec\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[1984,1987,1990],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"triage","ffffff",3558,"nuxt","ui","open","Padding and Sizing on UAvatar","2025-03-13T13:44:50Z","https://github.com/nuxt/ui/issues/3558",0.73411477,{"description":2002,"labels":2003,"number":2011,"owner":1994,"repository":2012,"state":1996,"title":2013,"updated_at":2014,"url":2015,"score":2016},"### Environment\n\nReproduction: https://stackblitz.com/edit/github-gu1sj1?file=tests%2Fbasic.e2e.test.ts\r\n\r\nI can't seem to utilize the alternative nuxt.config location with @nuxt/test-utils. If I have my nuxt.config as `./.config/nuxt.ts`, e2e tests will always fail with `Error: Invalid nuxt app. (Please explicitly set 'options.rootDir' pointing to a valid nuxt app)`.\r\n\r\nThis is my test:\r\n```js\r\n// ./tests/basic.e2e.test.ts\r\nimport { $fetch, setup } from '@nuxt/test-utils/e2e';\r\nimport { describe, expect, it } from 'vitest';\r\n\r\ndescribe('basic', async () => {\r\n await setup({\r\n rootDir: './app',\r\n configFile: '/.config/nuxt.ts',\r\n });\r\n\r\n it('contains Welcome to Nuxt! string', async () => {\r\n const html = await $fetch('/');\r\n expect(html).toContain('Welcome to Nuxt!');\r\n });\r\n});\r\n```\r\nand my nuxt.config:\r\n```js\r\n// ./.config/nuxt.ts\r\nexport default defineNuxtConfig({\r\n compatibilityDate: '2024-04-03',\r\n devtools: { enabled: true },\r\n future: {\r\n compatibilityVersion: 4,\r\n },\r\n modules: ['@nuxt/test-utils/module'],\r\n});\r\n```\r\nIf I move and rename nuxt.config back to the root, it works.\r\n\r\nI'm not sure if this is a limitation or expectation of test-utils of the config file name/location that isn't being honored by the `configFile` setting, or what.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-gu1sj1?file=tests%2Fbasic.e2e.test.ts\n\n### Describe the bug\n\nUsing alternative nuxt.config name/location causes e2e tests to fail.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2004,2005,2008],{"name":1985,"color":1986},{"name":2006,"color":2007},"vitest-environment","b60205",{"name":2009,"color":2010},"pending triage","5D08F5",893,"test-utils","e2e tests fail with `.config/nuxt.ts`","2024-08-09T04:45:20Z","https://github.com/nuxt/test-utils/issues/893",0.7444823,{"description":2018,"labels":2019,"number":2020,"owner":1994,"repository":2021,"state":2022,"title":2023,"updated_at":2024,"url":2025,"score":2026},"",[],1050,"nuxt.com","closed","[Code] Changelog","2023-10-10T14:45:04Z","https://github.com/nuxt/nuxt.com/issues/1050",0.4635123,{"description":2028,"labels":2029,"number":2031,"owner":1994,"repository":1995,"state":2022,"title":2032,"updated_at":2033,"url":2034,"score":2035},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v22.6.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.8.2\r\n- Builder: -\r\n- User Config: devtools, modules, compatibilityDate, imports\r\n- Runtime Modules: @nuxt/ui@2.18.4, @vueuse/nuxt@11.0.3\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\nlatest\r\n\r\n### Reproduction\r\n\r\nDoes not occur on Nuxt UI docs, as that component is out of sync with the real one in the examples. However, any project using the copyable component from the DatePicker docs will experience this.\r\n\r\n### Description\r\n\r\nThe source-provided DatePicker component in the docs is broken, and always shows the Range UI. This is because it checks to see if the date is an object (which it is no matter what), rather than checking if it has a start and end attribute like in the component actually used in the example. The two components should be brought in sync (I would do this but I'm unsure how many of the modifications are for displaying in docs.)\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_\r\n",[2030],{"name":1985,"color":1986},2082,"Date picker broken","2024-11-07T14:11:51Z","https://github.com/nuxt/ui/issues/2082",0.68749595,{"description":2037,"labels":2038,"number":2041,"owner":1994,"repository":1994,"state":2022,"title":2042,"updated_at":2043,"url":2044,"score":2045},"### Describe the feature\n\nTeleports suck cause they're not SSR friendly, but there's no other way to allow a page to fill in multiple separate areas (slots) defined by the layout. A classic example is that the main slot is for the main page content and then a second named slot could be used for the sidebar.\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [x] 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).",[2039],{"name":2009,"color":2040},"E99695",30563,"Named slots in layouts","2025-01-13T13:54:08Z","https://github.com/nuxt/nuxt/issues/30563",0.73671186,{"description":2047,"labels":2048,"number":2053,"owner":1994,"repository":1994,"state":2022,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### Environment\n\nNuxt 3.0.0-rc.11\n\n### Reproduction\n\nStackBlitz: https://stackblitz.com/edit/nuxt3-layout-slot-bug\n\n### Describe the bug\n\nLayout slots not working with default layout, generate error (see reproduction):\r\n\r\n```\r\nError: Codegen node is missing for element/if/for node. Apply appropriate transforms first.\r\n```\r\n\r\nNote the use of `app.vue`.\r\n\r\nExplicitly using `\u003CNuxtLayout>` with `layout: false` in page meta works but leads to full re-render of the layout and kinda defies the purpose of a default layout.\r\n\r\nNot sure if I'm doing something wrong with the setup, but following the docs, the code in the repro should work. Also, best in terms of DX IMO.\n\n### Additional context\n\nThis is a typical use case where you for instance have a nav and want to add additional items via a slot on specific pages.\n\n### Logs\n\n_No response_",[2049,2052],{"name":2050,"color":2051},"3.x","29bc7f",{"name":2009,"color":2040},15158,"Layout slots not working in default layout","2023-09-26T14:37:01Z","https://github.com/nuxt/nuxt/issues/15158",0.74205536,{"description":2059,"labels":2060,"number":2065,"owner":1994,"repository":1995,"state":2022,"title":2066,"updated_at":2067,"url":2068,"score":2069},"Exaggerating the issue:\n\n",[2061,2064],{"name":2062,"color":2063},"documentation","0075ca",{"name":1988,"color":1989},2477,"[Table] broken example in documentation on smaller screens","2024-10-28T15:55:20Z","https://github.com/nuxt/ui/issues/2477",0.7438608,{"description":2071,"labels":2072,"number":2076,"owner":1994,"repository":1994,"state":2022,"title":2077,"updated_at":2078,"url":2079,"score":2080},"Hey!\r\n\r\nWith our current project, me and the team was wondering what was the reasoning behind the decision to not support slots in layouts?\r\n\r\nWe ran into it when we realized that a CSS grid layout would work best for our responsive view, since each page knows what kind of sidebar or extra content is required in this specific case. For that the structure would need to be like this:\r\n\r\n```\r\nhtml\r\n head\r\n ...\r\n body\r\n my-header\r\n nuxt\r\n #content\r\n slot\r\n #sidebar\r\n slot(name=\"sidebar\")\r\n #extra\r\n slot(name=\"extra\")\r\n my-footer\r\n```\r\nRight now the two options we see are using a separate layout component or somehow coordinating sidebar and extra components to make their own requests according to current route, but both feel at odds with overall simplicity Nuxt aims for.\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/c941\">#c941\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2073],{"name":2074,"color":2075},"2.x","d4c5f9",1079,"Why no slots in layouts?","2023-01-18T15:40:44Z","https://github.com/nuxt/nuxt/issues/1079",0.7448867,{"description":2082,"labels":2083,"number":2091,"owner":1994,"repository":1994,"state":2022,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### Describe the feature\n\nWhen trying to setup my metadata, I need to inject some JS (GTM stuff), so I did use the \u003CScript> tag, but was surprised to see, that you are required to use the children prob and cant use the textContent/default slot, is there any reason for that?\r\n\r\nI tested locally that adding \r\n```js\r\n setup: setupForUseMeta((props, { slots }) => {\r\n const script = { ...props };\r\n const textContent = (slots.default?.() || []).filter(({ children }) => children).map(({ children }) => children).join(\"\");\r\n if (textContent) {\r\n script.children = textContent;\r\n }\r\n return {\r\n script: [script]\r\n };\r\n })\r\n```\r\ninto the setup function of the script component (https://github.com/nuxt/framework/blob/2e080c259fc5068fcc71e3790b4f5b75cef83eea/packages/nuxt/src/head/runtime/components.ts#L94, similarly to the noscript or style tags below) works just fine, so I would PR that as a solution if this feature request is accepted, but I want to hear your thoughts first before I setup a workspace.\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://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2084,2087,2088],{"name":2085,"color":2086},"enhancement","8DEF37",{"name":2050,"color":2051},{"name":2089,"color":2090},"🍰 p2-nice-to-have","0E8A16",15033,"Support using textContent of \u003CScript> head component","2023-01-19T17:44:04Z","https://github.com/nuxt/nuxt/issues/15033",0.75166035,{"labels":2097,"number":2100,"owner":1994,"repository":1994,"state":2022,"title":2101,"updated_at":2102,"url":2103,"score":2104},[2098,2099],{"name":2085,"color":2086},{"name":2074,"color":2075},6104,"Layout should be able to extend another layout (\"layout nesting\"?)","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/6104",0.7540351,["Reactive",2106],{},["Set"],["ShallowReactive",2109],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"ESrUuXS492SzKnArPoaMdF2klDa2BiTJFXWSS2c6zvU":-1},"/nuxt/test-utils/1050"]