work in Storybook? Thank you",[2001],{"name":2002,"color":2003},"question","d876e3",77,"icon","How do we make nuxt-icon work in Storybook?","2025-01-17T10:54:58Z","https://github.com/nuxt/icon/issues/77",0.7753768,{"description":2011,"labels":2012,"number":2017,"owner":1991,"repository":2018,"state":1993,"title":2019,"updated_at":2020,"url":2021,"score":2022},"**Describe the bug**\nWhen opening the tab on an app that uses a baseURL, the devtools `\u003Ciframe>` loads the incorrect URL\n\nThe `DEVTOOLS_UI_PATH` is set to `'/__nuxt-devtools-fonts'` but should support `'/prefix/__nuxt-devtools-fonts'` when a baseURL is defined\n\n**To reproduce**\nSet up your nuxt config with\n```js\n\tapp: {\n\t\tbaseURL: '/prefix/',\n\t},\n```\n\nYou will see the `\u003Ciframe src>` is lacking the baseURL. This is most noticeable when your app is served via a proxy\n\n**Additional context**\nI have seen other libraries join `nuxt.options.app.baseURL` to fix\n\n```js\naddCustomTab({\n view: {\n type: 'iframe',\n src: joinURL(nuxt.options.app?.baseURL, '/__nuxt-devtools-fonts'),\n```\n\nI will try to submit a PR with a fix but wanted to open this issue first",[2013,2014],{"name":1985,"color":1986},{"name":2015,"color":2016},"good first issue","7057ff",395,"fonts","devtools custom tab ignores app baseURL","2024-12-18T20:08:21Z","https://github.com/nuxt/fonts/issues/395",0.7798486,{"description":2024,"labels":2025,"number":2027,"owner":1991,"repository":2028,"state":2029,"title":2030,"updated_at":2031,"url":2032,"score":2033},"### 🐛 The bug\n\nThe type check `pnpm typecheck` failed with errors:\n\n```\nnode_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptCrisp.vue:45:13 - error TS7006: Parameter 'instance' implicitly has an 'any' type.\n\n45 onLoaded((instance) => {\n ~~~~~~~~\n\nnode_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptIntercom.vue:51:13 - error TS7006: Parameter 'instance' implicitly has an 'any' type.\n\n51 onLoaded((instance) => {\n ~~~~~~~~\n\nnode_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptLemonSqueezy.vue:30:24 - error TS7031: Binding element 'Setup' implicitly has an 'any' type.\n\n30 instance.onLoaded(({ Setup, Refresh }) => {\n ~~~~~\n\nnode_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptLemonSqueezy.vue:30:31 - error TS7031: Binding element 'Refresh' implicitly has an 'any' type.\n\n30 instance.onLoaded(({ Setup, Refresh }) => {\n ~~~~~~~\n\nnode_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptLemonSqueezy.vue:32:20 - error TS7006: Parameter 'event' implicitly has an 'any' type.\n\n32 eventHandler(event) {\n ~~~~~\n\n\nFound 5 errors in 3 files.\n\nErrors Files\n 1 node_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptCrisp.vue:45\n 1 node_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptIntercom.vue:51\n 3 node_modules/.pnpm/@nuxt+scripts@0.11.0_@unhead+vue@2.0.0-rc.9_vue@3.5.13_typescript@5.8.2___db0@0.3.1_ior_fe4ad10e210ec3a63dc66c405a2719e7/node_modules/@nuxt/scripts/dist/runtime/components/ScriptLemonSqueezy.vue:30\n\n ERROR Process exited with non-zero status (2) 12:42:19 AM\n\n at R._waitForOutput (node_modules/.pnpm/tinyexec@0.3.2/node_modules/tinyexec/dist/main.js:530:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async Object.run (node_modules/.pnpm/@nuxt+cli@3.22.5_magicast@0.3.5/node_modules/@nuxt/cli/dist/chunks/typecheck.mjs:44:7)\n at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:316:16)\n at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:307:11)\n at async runMain (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:445:7) \n\n\n\n ERROR Process exited with non-zero status (2) 12:42:19 AM\n\n ELIFECYCLE Command failed with exit code 1.\n```\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-zfwzy3du\n\n### 🌈 Expected behavior\n\nNo errors produced by `pnpm typecheck`\n\n### ℹ️ Additional context\n\nSteps to reproduce:\n1. Go to reproduction URL.\n2. Launch `pnpm typecheck` in the terminal.\n3. See the error output.",[2026],{"name":1985,"color":1986},419,"scripts","closed","Typecheck error [v0.11.0]","2025-03-13T04:26:07Z","https://github.com/nuxt/scripts/issues/419",0.71108276,{"description":2035,"labels":2036,"number":2040,"owner":1991,"repository":2041,"state":2029,"title":2042,"updated_at":2043,"url":2044,"score":2045},"- [ ] Invisible contrast https://www.notion.so/nuxt/Invisible-contrast-172c713f4cea43dc875fab68a76825be\n- [ ] Strange hover https://www.notion.so/nuxt/Strange-hover-5bb97015d8fc468485b7209d6f03bea8\n- [x] Broken images https://www.notion.so/nuxt/Broken-images-6b8c9cb921d34d3db8f27d9f5f36190a",[2037],{"name":2038,"color":2039},"needs refinement","A2C2AE",1092,"nuxt.com","[Review] Prose","2023-10-10T14:45:05Z","https://github.com/nuxt/nuxt.com/issues/1092",0.7314929,{"description":2047,"labels":2048,"number":2040,"owner":1991,"repository":2052,"state":2029,"title":2053,"updated_at":2054,"url":2055,"score":2045},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.15.1\n- Nuxt Version: 3.15.2\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.7.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules\n- Runtime Modules: @nuxt/test-utils/module@3.15.4\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/romhml/nuxt-test-repro\n\n### Describe the bug\n\nHi! There seems to be an issue when using `mountSuspended` on a component with `defineOptions({ inheritAttrs: false })` where attributes bound using `v-bind=\"$attrs\"` are missing.\n\nFor instance with this component:\n\n``` vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cbutton v-bind=\"$attrs\"> \u003Cslot /> \u003C/button>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\ndefineOptions({ inheritAttrs: false })\n\u003C/script>\n```\n\nThe first test below using `mountSuspended` will fail because the attribute is missing, whereas the test using ` mount` from ` @vue/test-utils` works as expected.\n\n``` ts\nimport { test, expect } from 'vitest'\nimport { mount } from '@vue/test-utils'\nimport { mountSuspended } from '@nuxt/test-utils/runtime'\nimport ExampleComponent from '~/app/components/ExampleComponent.vue'\n\ntest('with mountSuspended', async () => {\n const wrapper = await mountSuspended(ExampleComponent, { attrs: { 'aria-label': 'Aria Label' } })\n expect(wrapper.find('[aria-label=\"Aria Label\"]').exists()).toBe(true)\n})\n\n\ntest('with mount', () => {\n const wrapper = mount(ExampleComponent, { attrs: { 'aria-label': 'Aria Label' } })\n expect(wrapper.find('[aria-label=\"Aria Label\"]').exists()).toBe(true)\n})\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2049],{"name":2050,"color":2051},"pending triage","5D08F5","test-utils","`mountSuspended` fails to pass attributes when `inheritAttrs` is false","2025-02-01T13:02:07Z","https://github.com/nuxt/test-utils/issues/1092",{"description":2057,"labels":2058,"number":2062,"owner":1991,"repository":2052,"state":2029,"title":2063,"updated_at":2064,"url":2065,"score":2066},"I can't find a valid combination to use with Vuetify. I created an issue at `@nuxt-alt/vuetify`, where the `vite-plugin-vuetify` causes error `Vuetify plugin must be loaded after the vue plugin`:\r\n* https://github.com/nuxt-alt/vuetify/issues/9\r\n\r\nThis is caused by `vite:extendConfig` Nuxt hook not having the `vite:vue` Plugin accessible, so it can't reorder it. (Using `vite:configResolved` hook instead didn't work either.)\r\n\r\nNote that this issue only occurs when `vitest.config.mjs` is used, so I assume there may be some `nuxt-vitest`-specific zero-config Vite misconfiguration. I'd appreciate any hints about the root cause (or alternatives).",[2059],{"name":2060,"color":2061},"vitest-environment","b60205",591,"Incompatible with Vuetify","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/591",0.73571366,{"description":2068,"labels":2069,"number":2077,"owner":1991,"repository":1992,"state":2029,"title":2078,"updated_at":2079,"url":2080,"score":2081},"\u003C!-- **IMPORTANT!**\r\nBefore reporting a bug, please make sure that you have read through our documentation and you think your problem is indeed an issue related to our module. -->\r\n\r\n### Version\r\n@nuxt/ui: 2.8.1\r\n\r\n### Reproduction Link\r\nhttps://ui.nuxt.com/overlays/tooltip\r\n\r\n### Steps to reproduce\r\n1. Open NVDA or another screen reader\r\n2. Tab to the button which has a tooltip\r\n\r\n### What is Expected?\r\nThe tooltip should become visible on focus, and should be announced by the screen reader (probably by setting `aria-description` or `aria-describedby` on the element which receives focus)\r\n\r\n### What is actually happening?\r\nThe tooltip is not visible or announced.\r\n\r\nThis is an accessibility issue as the tooltip content isn't accessible to users who use keyboard-only navigation or screen readers.",[2070,2071,2074],{"name":1985,"color":1986},{"name":2072,"color":2073},"v3","49DCB8",{"name":2075,"color":2076},"reka-ui","56d799",687,"Tooltips are not keyboard-accessible or read by screen readers","2025-03-27T11:48:09Z","https://github.com/nuxt/ui/issues/687",0.75509405,{"description":2083,"labels":2084,"number":2088,"owner":1991,"repository":2041,"state":2029,"title":2089,"updated_at":2090,"url":2091,"score":2092},"Should be sent on `create` and `delete` webhooks",[2085],{"name":2086,"color":2087},"enhancement","1ad6ff",386,"[Live collab] Socket for branches","2022-04-26T13:32:01Z","https://github.com/nuxt/nuxt.com/issues/386",0.7570637,{"description":2094,"labels":2095,"number":2088,"owner":1991,"repository":2028,"state":2029,"title":2097,"updated_at":2098,"url":2099,"score":2092},"### 🐛 The bug\n\nI'm facing an issue while integrating Google AdSense using `nuxt/script`. The script is being injected correctly, but AdSense throws warnings related to unsupported attributes in the `\u003Chead>` tag. \n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-qoe9bjl4?file=pages%2Findex.vue\n\n### 🌈 Expected behavior\n\nThe AdSense script should load without warnings.\n\n### ℹ️ Additional context\n\nAdSense console logs the following errors:\n\n\n\nBut ads are load properly.",[2096],{"name":1985,"color":1986},"Google AdSense Integration Issue – Unsupported Attributes in Head Tag","2025-02-22T03:40:13Z","https://github.com/nuxt/scripts/issues/386",["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"A4EgN3QexxXII2rT_J9dv2gKHEfANr867iekjRe9YB8":-1},"/nuxt/icon/265"]