",[1984,1987,1990],{"name":1985,"color":1986},"enhancement","a2eeef",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"triage","ffffff",3270,"nuxt","ui","open","[Feature request] Toast hide progress in app.config","2025-02-09T17:11:11Z","https://github.com/nuxt/ui/issues/3270",0.70339644,{"description":2002,"labels":2003,"number":2004,"owner":1994,"repository":2005,"state":1996,"title":2006,"updated_at":2007,"url":2008,"score":2009},"Hi team, \r\n\r\nThis time i founded this vulnerability in your website: \r\nhttps://nuxtjs.org/\r\n\r\n\r\n\r\nClick jacking (User Interface redress attack, UI redress attack, UI redressing) is a malicious technique of tricking a Web user into clicking on something different from what the user perceives they are clicking on, thus potentially revealing confidential information or taking control of their computer while clicking on seemingly innocuous web pages.\r\n\r\nThe server didn't return an X-Frame-Options header which means that this website could be at risk of a click jacking attack. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a \u003Cframe> or \u003Ciframe>. Sites can use this to avoid click jacking attacks, by ensuring that their content is not embedded into other sites.\r\n\r\nThis vulnerability affects Web Server.\r\n\r\nHere are the steps to reproduce the vulnerability:\r\n\r\n1.open notepad and paste the following code.\r\n\u003C!DOCTYPE HTML>\r\n\u003Chtml lang=\"en-US\">\r\n\u003Chead>\r\n\u003Cmeta charset=\"UTF-8\">\r\n\u003Ctitle>i Frame\u003C/title>\r\n\u003C/head>\r\n\u003Cbody>\r\n\u003Ch3>This is clickjacking vulnerable\u003C/h3>\r\n\u003Ciframe src=\" https://nuxtjs.org/ \" frameborder=\"2 px\" height=\"500px\" width=\"500px\">\u003C/iframe>\r\n\u003C/body>\r\n\u003C/html>\r\n\r\n2.save it as \u003Canyname>.html eg s.html\r\n\r\n3.and just simply open that...\r\n\r\nOR\r\nCopy the link below and paste on your updated browser (Chrome,Firefox).\r\nhttps://clickjacker.io/test?url=https://nuxtjs.org/\r\nAs far as i know this data is enough to prove that your site is vulnerable to Click jacking\r\naccording to OWASP its more than enough.\r\n\r\nhttps://www.owasp.org/index.php/Testing_for_Clickjacking_(OWASP-CS-004) \r\n\r\nSOLUTION: \r\n\r\nhttps://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet\r\n\r\nCheck this out and here is the solution for that.\r\n \r\n\r\nI Hope that you will fix this issue as soon as possible. Looking forward to hear from you. Thank you\r\n\r\nSincerely,\r\nHassan Raza\r\n",[],1456,"nuxt.com","Vulnerability type Click Jacking","2023-12-27T17:14:15Z","https://github.com/nuxt/nuxt.com/issues/1456",0.73510885,{"description":2011,"labels":2012,"number":2017,"owner":1994,"repository":1995,"state":2018,"title":2019,"updated_at":2020,"url":2021,"score":2022},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.13.1\n- CLI Version: 3.13.1\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, ui, colorMode, compatibilityDate, icon, sourcemap, experimental, nitro, future, pwa, routeRules, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @vueuse/nuxt@10.11.1, @nuxtjs/mdc@0.6.1, @formkit/auto-animate/nuxt@0.8.2, @vite-pwa/nuxt@0.10.5\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n`style tag`\n\n`Use`\n\n`debug`\n\n\n\n### Description\n\nSorry, I don't know if it's a bad configuration on my part, however the styles in which I use @apply don't work for me.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2013,2016],{"name":2014,"color":2015},"bug","d73a4a",{"name":1988,"color":1989},2763,"closed","postcss style not applying","2024-12-05T13:48:59Z","https://github.com/nuxt/ui/issues/2763",0.6865504,{"description":2024,"labels":2025,"number":2026,"owner":1994,"repository":2027,"state":2018,"title":2028,"updated_at":2029,"url":2030,"score":2031},"\r\nI get warn: `Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.` when I use an icon component and use multiple slots at the same time.\r\n\r\n# Replication:\r\nnuxt.config.ts\r\n```javascript\r\nexport default defineNuxtConfig({\r\n devtools: { enabled: true },\r\n modules: ['@nuxt/content', \"nuxt-icon\"],\r\n content: {\r\n documentDriven: {\r\n trailingSlash: false\r\n }\r\n }\r\n})\r\n```\r\ncomponents/content/ComponentWithIcon.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n Component with icon:\r\n \u003CIcon name=\"bxl:python\" class=\"w-8 h-8\" />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncomponents/content/Container.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nlayouts/full.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"custom-layout\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncontent/index.md:\r\n```markdown\r\n---\r\nlayout: 'full'\r\n---\r\n\r\n:component-with-icon\r\n\r\n::container\r\nSlot nr 1\r\n::::container\r\nSlot nr 2\r\n::::\r\n::\r\n```\r\n\r\nThis bug prevents the site from being used in development mode due to the infinity loop. The problem does not occur in the latest beta version of nuxt-icon, but in the original project I use nuxt-ui, which uses the old version \r\n",[],157,"icon","Infinite WARN loop with slots and nuxt-content","2024-09-06T11:17:31Z","https://github.com/nuxt/icon/issues/157",0.689753,{"description":2033,"labels":2034,"number":2038,"owner":1994,"repository":1994,"state":2018,"title":2039,"updated_at":2040,"url":2041,"score":2042},"In non nuxjs apps you put code that has run once on app startup in main.js or app.vue. Both are not available in nuxtjs. Where do I put this code?\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/c718\">#c718\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2035],{"name":2036,"color":2037},"2.x","d4c5f9",837,"Where to put code that runs once on app startup (no main.js)","2023-01-18T15:39:53Z","https://github.com/nuxt/nuxt/issues/837",0.7151164,{"description":2044,"labels":2045,"number":2055,"owner":1994,"repository":1994,"state":2018,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### Describe the feature\r\n\r\nCan you allow import nuxt component into a basic vue app\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2046,2049,2052],{"name":2047,"color":2048},"discussion","538de2",{"name":2050,"color":2051},"3.x","29bc7f",{"name":2053,"color":2054},"needs details","493824",15584,"Use Nuxt component in vue app","2023-02-06T10:29:55Z","https://github.com/nuxt/nuxt/issues/15584",0.7227624,{"labels":2061,"number":2070,"owner":1994,"repository":1994,"state":2018,"title":2071,"updated_at":2072,"url":2073,"score":2074},[2062,2063,2066,2067],{"name":2050,"color":2051},{"name":2064,"color":2065},"dx","C39D69",{"name":2014,"color":2015},{"name":2068,"color":2069},"🔨 p3-minor","FBCA04",13176,"Errors when using a Vue components library using defineNuxtModule and third party dependencies","2023-01-19T16:48:30Z","https://github.com/nuxt/nuxt/issues/13176",0.73450094,{"description":2076,"labels":2077,"number":2078,"owner":1994,"repository":2005,"state":2018,"title":2079,"updated_at":2080,"url":2081,"score":2082},"Open https://nuxt.com/docs/guide/directory-structure/composables, **Introduction** page is shown instead of **Composables**\n\n\n\nI think the regression is due to 43b0f43",[],1752,"All docs/[...slug] routes show Introduction page","2025-01-14T11:25:53Z","https://github.com/nuxt/nuxt.com/issues/1752",0.7347433,{"description":2084,"labels":2085,"number":2089,"owner":1994,"repository":1994,"state":2018,"title":2090,"updated_at":2091,"url":2092,"score":2093},"### What problem does this feature solve?\n\n`vue-perf-devtools` is an awesome extension to the regular `vue-dev-tools`.\nCurrently I have to use a custom plugin to support it: https://github.com/wemake-services/wemake-vue-template/blob/master/template/client/plugins/performance.js\n\nThis plugin is rather simple:\n\n```js\nimport Vue from 'vue'\n\nVue.config.performance = process.env.NODE_ENV === 'development'\n```\n\nBut maybe it is worth to support it out of the box?\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c7219\">#c7219\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2086,2088],{"name":1985,"color":2087},"8DEF37",{"name":2036,"color":2037},3427,"Native vue-perf-devtool support","2023-01-22T15:50:41Z","https://github.com/nuxt/nuxt/issues/3427",0.73550946,{"description":2095,"labels":2096,"number":2106,"owner":1994,"repository":2107,"state":2018,"title":2108,"updated_at":2109,"url":2110,"score":2111},"I'm going to preface this by saying I'm an experienced backend developer who has recently been diving into the world of nuxt/vue/nodejs etc., so I apologize in advance if I'm making an obvious oversight.\r\n\r\nI'm trying to add Vue component testing to an already established project and am having trouble with integrating the `nuxt-vitest` package. \r\n\r\nSpecifically, I'm having the issue of `npm run dev` failing with an `error while updating dependencies` as shown below:\r\n\u003Cimg width=\"985\" alt=\"image\" src=\"https://github.com/danielroe/nuxt-vitest/assets/127154893/1c1b0142-c463-4e2b-8a3c-db14b8120ab9\">\r\n\r\nThis error starts happening as soon as I add `import { mountSupsended } from 'nuxt-vitest/utils'` to my `nuxt.test.js` file that is in a subfolder inside my `components` directory.\r\n\r\nHere are my dependencies:\r\n```\r\n \"devDependencies\": {\r\n \"@tailwindcss/forms\": \"^0.5.3\",\r\n \"@vue/test-utils\": \"^2.4.1\",\r\n \"@vueuse/core\": \"^9.10.0\",\r\n \"@vueuse/nuxt\": \"^9.10.0\",\r\n \"autoprefixer\": \"^10.4.13\",\r\n \"happy-dom\": \"^10.11.2\",\r\n \"html5-qrcode\": \"^2.3.8\",\r\n \"nuxt\": \"^3.2.3\",\r\n \"nuxt-vitest\": \"^0.11.0\",\r\n \"postcss\": \"^8.4.19\",\r\n \"react\": \"^18.2.0\",\r\n \"react-dom\": \"^18.2.0\",\r\n \"tailwindcss\": \"^3.2.4\",\r\n \"vitest\": \"^0.33.0\"\r\n },\r\n \"dependencies\": {\r\n \"@formkit/nuxt\": \"^0.17.2\",\r\n \"@pinia/nuxt\": \"^0.4.11\",\r\n \"@sphereon/isomorphic-argon2\": \"^1.0.1\",\r\n \"@vueuse/components\": \"^9.10.0\",\r\n \"@vueuse/integrations\": \"^9.10.0\",\r\n \"buffer\": \"^6.0.3\",\r\n \"dayjs\": \"^1.11.7\",\r\n \"focus-trap\": \"^7.2.0\",\r\n \"pinia\": \"^2.1.6\",\r\n \"prettier\": \"^2.8.3\"\r\n },\r\n```\r\n\r\nIt is currently running with Nuxt 3.7.4\r\n\r\nI have tried and failed to reproduce this on a smaller toy repo.\r\n\r\nMight you have any pointers for figuring out what is going on here? I've spent the last two days trying to figure this out.",[2097,2100,2103],{"name":2098,"color":2099},"vitest-environment","b60205",{"name":2101,"color":2102},"needs reproduction","DE7793",{"name":2104,"color":2105},"closed-by-bot","ededed",599,"test-utils","Issues resolving dependencies when running `nuxt dev`","2023-12-10T01:51:33Z","https://github.com/nuxt/test-utils/issues/599",0.7358758,["Reactive",2113],{},["Set"],["ShallowReactive",2116],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"C03F09IohTmft81TWfHMX3Ebc1ZNSeEIpVQQWALo20M":-1},"/nuxt/ui/3247"]