\n \u003C/UCarousel>\n\u003C/template>\n```\n\nAnd I get some TypeScript errors:\n\nProperty 'page' does not exist on type 'CreateComponentPublicInstanceWithMixins(...)\nProperty 'select' does not exist on type 'CreateComponentPublicInstanceWithMixins(...)\nProperty 'next' does not exist on type 'CreateComponentPublicInstanceWithMixins(...)\n\nHow should I correctly infer the type for UCarousel?\n\nNuxt v3.15.1\nNuxtUI v2.20.0",[1984,1987],{"name":1985,"color":1986},"question","d876e3",{"name":1988,"color":1989},"stale","ededed",3053,"nuxt","ui","open","How to properly use UCarousel API with TypeScript","2025-02-09T02:00:51Z","https://github.com/nuxt/ui/issues/3053",0.669664,{"description":1999,"labels":2000,"number":2001,"owner":1991,"repository":2002,"state":1993,"title":2003,"updated_at":2004,"url":2005,"score":2006},"The current example [deployment](https://nuxt.com/deploy/github-pages) script generates warnings due to the actions using deprecated versions.\r\n\r\nI also use `pnpm` locally, so an example of how to get started with `pnpm` as well as `npm` would be nice.\r\n\r\nI'm not sure what the preset does in `npx nuxt build --preset github_pages` and if that's the same as the [Nitro preset](https://nitro.unjs.io/deploy/providers/github-pages)?\r\n\r\nMy own static page could be deployed using `pnpm generate` with this `deploy.yaml` script:\r\n\r\n```yaml\r\n# https://github.com/actions/deploy-pages#usage\r\nname: Deploy to GitHub Pages\r\n\r\non:\r\n push:\r\n branches: [main]\r\n\r\n workflow_dispatch:\r\n\r\n# Grant GITHUB_TOKEN the permissions required to make a Pages deployment\r\npermissions:\r\n contents: read\r\n pages: write # to deploy to Pages\r\n id-token: write # to verify the deployment originates from an appropriate source\r\n\r\njobs:\r\n build:\r\n runs-on: ubuntu-latest\r\n steps:\r\n - name: Checkout\r\n uses: actions/checkout@v4\r\n - name: Setup PNPM\r\n uses: pnpm/action-setup@v3\r\n with:\r\n version: 9.0.x\r\n - name: Setup Node\r\n uses: actions/setup-node@v4\r\n with:\r\n node-version: \"20\"\r\n # Pick your own package manager and build script\r\n - name: Install dependencies\r\n run: pnpm install\r\n - name: Build nuxt\r\n run: pnpm generate\r\n - name: Upload artifact\r\n uses: actions/upload-pages-artifact@v3\r\n with:\r\n path: ./.output/public\r\n\r\n # Deployment job\r\n deploy:\r\n environment:\r\n name: github_pages\r\n url: ${{ steps.deployment.outputs.page_url }}\r\n needs: build\r\n runs-on: ubuntu-latest\r\n steps:\r\n - name: Deploy to GitHub Pages\r\n id: deployment\r\n uses: actions/deploy-pages@v4\r\n```\r\n\r\nI'm hesitant to update the docs with this example myself when I don't fully understand it all yet, but maybe this could be useful as a starter to someone with more knowledge then me (or future me).\r\n\r\nI took some inspiration from the [Vitepress](https://vitepress.dev/guide/deploy#github-pages) example, which is why a couple of things have been moved or reformatted slightly.\r\n\r\n---\r\n\r\nEdit: remove `- run: corepack enable` as I don't think its necessary.",[],1578,"nuxt.com","PNPM Deployment to GitHub Pages","2024-09-26T14:12:35Z","https://github.com/nuxt/nuxt.com/issues/1578",0.6883709,{"description":2008,"labels":2009,"number":2019,"owner":1991,"repository":2020,"state":1993,"title":2021,"updated_at":2022,"url":2023,"score":2024},"Hey, firstly thank you for making this plugin, it looks very useful :)\r\n\r\nRunning this module seems to run the whole nuxt environment, including the plugins, and we have a plugin that makes a api call. We normally just mock the module where we import the api function but it doesn't seem to work in this case. For example:\r\n```\r\n// somePlugin.ts\r\nimport { fetchProducts } from \"~/service/products\";\r\n\r\nexport default defineNuxtPlugin(async () => {\r\n const products = fetchProducts();\r\n // do something with the products\r\n});\r\n```\r\n\r\n```\r\n// SomeComponent.nuxt.spec.js\r\nimport { describe, it, expect, vi } from \"vitest\";\r\nimport { shallowMount } from \"@vue/test-utils\";\r\nimport SomeComponent from \"../SomeComponent.vue\";\r\n\r\n// trying to mock the products service so that the real api doesn't get called during the plugins\r\nvi.mock(\"~/service/products\");\r\n\r\ndescribe(\"SomeComponent\", async () => {\r\n it(\"Is a Vue instance\", () => {\r\n const wrapper = shallowMount(SomeComponent);\r\n expect(wrapper.vm).toBeTruthy();\r\n });\r\n});\r\n```\r\n\r\nI assume these mocks only work for the component that we are testing and not for the plugins in the nuxt environment for example. Do you have a suggestion about how to solve this?",[2010,2013,2016],{"name":2011,"color":2012},"documentation","0075ca",{"name":2014,"color":2015},"enhancement","a2eeef",{"name":2017,"color":2018},"vitest-environment","b60205",544,"test-utils","mocking plugins used within nuxt","2024-07-23T12:17:21Z","https://github.com/nuxt/test-utils/issues/544",0.69088924,{"description":2026,"labels":2027,"number":2029,"owner":1991,"repository":1992,"state":1993,"title":2030,"updated_at":2031,"url":2032,"score":2033},"### Description\n\nHow to configure Nuxt Color Mode in Nuxt UI so that it does not inject color styles for all Nuxt UI components using inline styles",[2028],{"name":1985,"color":1986},3394,"implement csp, sty-src with nonce","2025-02-25T10:13:42Z","https://github.com/nuxt/ui/issues/3394",0.71054083,{"description":2035,"labels":2036,"number":2037,"owner":1991,"repository":2038,"state":1993,"title":2039,"updated_at":2040,"url":2041,"score":2042},"It would be nice if you could alias and entire collection instead of just an icon.\n\nRight now I do it this way.\n```ts\nconst createIconAliases = (newPrefix: string, iconifyJson: IconifyJSON) => {\n const exisitngPrefix = iconifyJson.prefix;\n const icons = Object.keys(iconifyJson.icons);\n\n return icons.reduce(\n (object, value) => {\n object[`${newPrefix}:${value}`] = `${exisitngPrefix}:${value}`;\n return object;\n },\n {} as Record\u003Cstring, string>,\n );\n};\n```",[],362,"icon","[feature request] Allow aliasing entire collection","2025-02-21T20:10:51Z","https://github.com/nuxt/icon/issues/362",0.7113872,{"description":2044,"labels":2045,"number":2053,"owner":1991,"repository":1992,"state":1993,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nUTabs documentation could benefit from an example of how to use it to display nested pages. An example use case could be a profile page with tabs for profile information and settings, where navigating through each would lead to a sub-page (profile information being in /profile, and settings being in /profile/settings)\n\n### Additional context\n\n_No response_",[2046,2047,2050],{"name":2014,"color":2015},{"name":2048,"color":2049},"v3","49DCB8",{"name":2051,"color":2052},"triage","ffffff",2872,"[v3 docs]: example for nested pages with UTabs","2024-12-16T09:46:36Z","https://github.com/nuxt/ui/issues/2872",0.7149596,{"description":2059,"labels":2060,"number":2067,"owner":1991,"repository":1991,"state":2068,"title":2069,"updated_at":2070,"url":2071,"score":2072},"### Version\n\n[v2.4.3](https://github.com/nuxt.js/releases/tag/v2.4.3)\n\n### Reproduction link\n\n[https://github.com/kdeng/nuxt-named-view-sample](https://github.com/kdeng/nuxt-named-view-sample)\n\n### Steps to reproduce\n\n1. Run `npm i`\n2. Run `npm run dev`\n\n### What is expected ?\n\nI expected router.js can be generated properly, and named view can be rendered properly.\n\n### What is actually happening?\n\nrouter.js has been generated with syntax error.\n\n```\n ERROR Failed to compile with 1 errors friendly-errors 22:13:34\n\n\n ERROR in ./.nuxt/router.js friendly-errors 22:13:34\n\nSyntax Error: Unexpected token, expected \",\" (86:8) friendly-errors 22:13:34\n\n 84 | default: _708facd7,\n 85 | footer: _03b372e3\n> 86 | default: _6fab42f0,\n | ^\n 87 | top: _6b7085a2\n 88 | },\n 89 | name: \"main\"\n\n friendly-errors 22:13:34\n @ ./.nuxt/index.js 8:0-43 59:19-31\n @ ./.nuxt/client.js\n @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true&timeout=30000&ansiColors=&overlayStyles=&name=client&path=/__webpack_hmr/client ./.nuxt/client.js\n friendly-errors 22:13:34\nℹ Waiting for file changes\n\n```\n\n### Additional comments?\n\nI am new to nuxtjs, and try to play around about named views for enabling master footer component for cart router, I am not sure whether it is my mistake or a bug. Cheers.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8715\">#c8715\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2061,2064],{"name":2062,"color":2063},"pending triage","E99695",{"name":2065,"color":2066},"2.x","d4c5f9",5096,"closed","multiple named views cause router.js contains syntax error","2023-01-22T15:33:01Z","https://github.com/nuxt/nuxt/issues/5096",0.69166994,{"description":2074,"labels":2075,"number":2080,"owner":1991,"repository":1991,"state":2068,"title":2081,"updated_at":2082,"url":2083,"score":2084},"\r\nFirst up: I don't know if this is the right project to post it, but it might be in the intrest of the Less.js project to work with vite, I hope.\r\n\r\n\r\n### Environment\r\n\r\n- `less` version: 4.2.0\r\n- `nodejs` version: 20.9.0\r\n- vite@5.0.10\r\n- nuxt@3.9.0\r\n- `operating system`: debian\r\n\r\n\r\n### Error\r\n\r\n```\r\n[vite-node] [plugin:vite:vue] [SyntaxError] ./node_modules/.pnpm/nuxt@3.9.0_less@4.2.0_vite@5.0.10/node_modules/nuxt/dist/app/components/nuxt-root.vue:3:5\r\n```\r\n\r\n```\r\n ERROR Pre-transform error: @vnode-* hooks in templates are no longer supported. Use the vue: prefix instead. For example, @vnode-mounted should be changed to @vue:mounted. @vnode-* hooks support has been removed in 3.4.\r\n```\r\n\r\n\r\n### Reproduction\r\n\r\ncodesandbox.io\r\n1. nuxt3 framework\r\n2. template with lang=\"less\" (aktually not needed, having installed by `pnpm` and runnung `npm run dev` through nuxi->vite is enough to error out)\r\n\r\nand it brakes.\r\n\r\n### Describe the bug\r\n\r\n\u003C!-- A clear and concise description of what the bug is -->\r\n\r\n**Expected behavior:**\r\n\r\nto work with vite\r\n",[2076,2079],{"name":2077,"color":2078},"3.x","29bc7f",{"name":2062,"color":2063},25142,"error on compiling using less","2024-01-10T17:43:59Z","https://github.com/nuxt/nuxt/issues/25142",0.6999359,{"description":2086,"labels":2087,"number":2090,"owner":1991,"repository":1992,"state":2068,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\nIs there a way we can add a custom class to the tag `\u003Cth>`, in my case I would like to place `w-28` so that it has a fixed width\n\n\n\n\n",[2088,2089],{"name":1985,"color":1986},{"name":2048,"color":2049},2762,"[v3] Custom class to the tag \u003Cth>","2024-12-09T11:14:42Z","https://github.com/nuxt/ui/issues/2762",0.7010293,{"description":2096,"labels":2097,"number":2098,"owner":1991,"repository":2002,"state":2068,"title":2099,"updated_at":2100,"url":2101,"score":2102},"Hello there!\r\n\r\nEvery since your beautiful new website update, our Nuxt 3 module, `sidebase/nuxt-auth` has been displaying the message: \"This module is not yet compatible with Nuxt 3\".\r\n\r\n\r\n\r\nInside of our [file in this repo](https://github.com/nuxt/modules/blob/main/modules/sidebase-auth.yml), we do list that we support Nuxt 3. How do we resolve this issue? Is there something we need to update here to ensure this message goes away? \r\n\r\nThank you very much!",[],1395,"Since website update, some Nuxt 3 modules, display they are not compatible with Nuxt 3","2023-10-25T10:25:05Z","https://github.com/nuxt/nuxt.com/issues/1395",0.70155394,["Reactive",2104],{},["Set"],["ShallowReactive",2107],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"nm0tWCDjjK0K98T5bwlMXFVmJOKdYKahNjL-dEYCQj8":-1},"/nuxt/test-utils/927"]