\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.71108544,{"description":2905,"labels":2906,"number":2907,"owner":2877,"repository":2908,"state":2890,"title":2909,"updated_at":2910,"url":2911,"score":2912},"I am using the module with `fontshare` as a provider. When checking `pageInsights` it shows that `@font-face` is not being used. When adding `fontain` module it resolves the issue.\r\n\r\n\u003Cimg width=\"741\" alt=\"Screenshot 2024-06-22 at 23 39 50\" src=\"https://github.com/nuxt/fonts/assets/33263129/a91b98cd-7b15-4a13-9588-35bd8c0a0366\">\r\n\r\n\r\n\u003Cimg width=\"663\" alt=\"Screenshot 2024-06-22 at 22 38 07\" src=\"https://github.com/nuxt/fonts/assets/33263129/0fe5a298-1dd2-4fb3-b476-520be7d2ac08\">\r\n\r\n\r\nwhen using `fontain`\r\n\r\n\r\n\u003Cimg width=\"964\" alt=\"Screenshot 2024-06-22 at 22 34 07\" src=\"https://github.com/nuxt/fonts/assets/33263129/dca00dbe-a0bc-4163-a55b-e584f97a2506\">\r\n\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.14.0`\r\n- Nuxt Version: `3.12.2`\r\n- CLI Version: `3.12.0`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `npm@10.7.0`\r\n- Builder: `-`\r\n- User Config: `devtools`, `future`, `modules`, `runtimeConfig`, `app`, `routeRules`, `devServer`, `build`, `fonts`, `tailwindcss`\r\n- Runtime Modules: `@nuxt/eslint@0.3.13`, `@nuxtjs/tailwindcss@6.12.0`, `@nuxt/image@1.7.0`, `@nuxt/fonts@0.7.0`, `@nuxtjs/fontaine@0.4.3`\r\n- Build Modules: `-`\r\n",[],182,"fonts","`@font-face` not used with `fontshare` provider","2024-09-23T12:32:00Z","https://github.com/nuxt/fonts/issues/182",0.7191532,{"description":2914,"labels":2915,"number":2919,"owner":2877,"repository":2877,"state":2890,"title":2920,"updated_at":2921,"url":2922,"score":2923},"I was wondering if it's possible to have support separate files so that we can have better IDE autocompletion support for TypeScript or JS. Currently code intelligence is a problem with `.vue` files.\r\n\r\nWe can split the components into `html`, `js` and `css` by `require` (requiring) the html and css files - but with `pages` directory as it's translated to routes, I'm not sure how will the above work.\r\n\r\nAlso, having separated `css` and `scss` file means that we have to figure out how to write scoped css/scss as I'm not sure how to do it without css-modules currently.\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/c696\">#c696\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2916],{"name":2917,"color":2918},"2.x","d4c5f9",810,"Separate .vue into html, js and css files","2023-01-18T15:39:48Z","https://github.com/nuxt/nuxt/issues/810",0.72228426,{"description":2925,"labels":2926,"number":2931,"owner":2877,"repository":2877,"state":2890,"title":2932,"updated_at":2933,"url":2934,"score":2935},"I'm trying to include flowtype support in my app, but its throwing error and so far i have been unable to solve the issue. P.S. I do have a vue.js project with this exact same config and it works.\r\n\r\n```\r\n.babelrc\r\n{\r\n \"presets\": [\r\n [\"env\", { \"modules\": false }],\r\n \"stage-2\",\r\n [\"es2015\", {\"modules\": false }],\r\n \"flow-vue\"\r\n ],\r\n \"plugins\": [\r\n \"transform-runtime\",\r\n \"babel-plugin-transform-class-properties\",\r\n \"syntax-flow\",\r\n \"babel-plugin-transform-flow-strip-types\"\r\n ],\r\n \"comments\": false\r\n}\r\n```\r\n\r\n```\r\n.eslintrc.js\r\n// http://eslint.org/docs/user-guide/configuring\r\n\r\nmodule.exports = {\r\n root: true,\r\n parserOptions: {\r\n parser: 'babel-eslint',\r\n sourceType: 'module'\r\n },\r\n env: {\r\n browser: true,\r\n node: true\r\n },\r\n // https://github.com/feross/standard/blob/master/RULES.md#javascript-standard-style\r\n extends: [\r\n 'standard',\r\n 'plugin:flowtype/recommended'\r\n ],\r\n // required to lint *.vue files\r\n plugins: [\r\n 'html',\r\n 'flowtype-errors',\r\n 'flowtype'\r\n ],\r\n // add your custom rules here\r\n 'rules': {\r\n 'flowtype-errors/show-errors': 2,\r\n // allow paren-less arrow functions\r\n 'arrow-parens': 0,\r\n 'semi': [\"error\", \"always\"],\r\n // allow async-await\r\n 'generator-star-spacing': 0,\r\n // allow debugger during development\r\n 'no-debugger': process.env.NODE_ENV === 'production' ? 2 : 0\r\n }\r\n}\r\n```\r\n```\r\n.flowconfig\r\n[include]\r\npages/**/.*\r\ncomponents/**/.*\r\nplugins/.*\r\n\r\n[ignore]\r\n.*/build/.*\r\n.*/config/.*\r\n.*/dist/.*\r\n.*/node_modules/.*\r\n.*/static/.*\r\n.*/test/.*\r\n.*/ssl/.*\r\n\r\n[libs]\r\n./flow/\r\n\r\n[options]\r\nemoji=true\r\nmodule.file_ext=.vue\r\nmodule.file_ext=.js\r\nserver.max_workers=3\r\nlog.file=./flow.log\r\nsuppress_comment= \\\\(.\\\\|\\n\\\\)*\\\\$FlowFixMe\r\nunsafe.enable_getters_and_setters=true\r\nmodule.system.node.resolve_dirname=node_modules\r\nmodule.name_mapper='^.*\\.css$' -> 'empty/object'\r\nmodule.name_mapper='^.*\\.js$' -> 'empty/object'\r\n```\r\n\r\n```\r\npages/index.vue\r\nmethods: {\r\n testing(param: Object) {\r\n\r\n }\r\n }\r\n```\r\n\r\nOn running ```npm run dev```\r\n\r\n\r\nthis is the error i get.\r\n\r\nAlso, if i run ```node_modules/.bin/flow check``` it works properly. And if i remove the flowtypes, eslint throws error to add flowtype annotations. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1417\">#c1417\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2927,2930],{"name":2928,"color":2929},"good first issue","fbca04",{"name":2917,"color":2918},1588,"flowtype support","2023-02-06T11:24:57Z","https://github.com/nuxt/nuxt/issues/1588",0.7228928,{"description":2937,"labels":2938,"number":2939,"owner":2877,"repository":2940,"state":2890,"title":2941,"updated_at":2942,"url":2943,"score":2944},"\r\n\r\nTested on Mac/Windows on Safari, Chrome, Arc Browser, even with Incognito.\r\n\r\nConsole:\r\n\r\n\r\nThis might be related to nuxt/image?\r\n",[],1636,"nuxt.com","\"built by developers\" home section icons do not display","2024-08-16T18:08:46Z","https://github.com/nuxt/nuxt.com/issues/1636",0.72338164,{"description":2946,"labels":2947,"number":2963,"owner":2877,"repository":2877,"state":2890,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v20.1.0\r\n- Nuxt Version: 3.5.2\r\n- Nitro Version: 2.4.1\r\n- Package Manager: npm@9.6.4\r\n- Builder: vite\r\n- User Config: modules, app, typescript, vite, experimental\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @vueuse/nuxt@10.1.2\r\n- Build Modules: -\n\n### Reproduction\n\nI have a plugin for i18n which uses `\"i18next\": \"^22.5.0\",\"i18next-vue\": \"^2.1.1\",`\r\n\r\n```typescript\r\nexport default defineNuxtPlugin(({ vueApp }) => {\r\n\tvueApp.use(I18NextVue, { i18next });\r\n\ti18next.init({ fallbackLng: defaultLocale, resources });\r\n\r\n\tfunction translate(key: TranslationKeys) {\r\n\t\tconst { t } = useTranslation();\r\n\t\treturn t(key);\r\n\t}\r\n\r\n\treturn { provide: { i18n: i18next, translate } };\r\n});\r\n```\n\n### Describe the bug\n\nBut when I use my plugin like this\r\n```typescript\r\nconst { $translate } = useNuxtApp();\r\nuseHead({ titleTemplate: (t) => `${t} / ${$translate('meta.home.title')}` });\r\n```\r\nI get the following error.\r\n\r\n\r\nThis works fine tho\r\n```typescript\r\nconst { $translate } = useNuxtApp();\r\nuseHead({ titleTemplate: `%s / ${$translate('meta.home.title')}` });\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[frontend] [nuxt] [request error] [unhandled] [500] i18next-vue: No Vue instance in context. Make sure to register the i18next-vue plugin using app.use(...).\r\n[frontend] at Module.useTranslation (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/i18next-vue/dist/index.mjs:118:11)\r\n[frontend] at translate (C:\\Users\\ckuka\\VS Code Projects\\ows-events\\frontend\\plugins\\i18n.ts:23:41)\r\n[frontend] at titleTemplate (C:\\Users\\ckuka\\VS Code Projects\\ows-events\\frontend\\pages\\index.vue:43:39)\r\n[frontend] at resolveTitleTemplate (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/@unhead/shared/dist/index.mjs:79:12)\r\n[frontend] at tags:resolve (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/unhead/dist/index.mjs:59:28)\r\n[frontend] at /C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/hookable/dist/index.mjs:48:66\r\n[frontend] at /C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/hookable/dist/index.mjs:48:56\r\n[frontend] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n[frontend] at async Object.resolveTags (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/unhead/dist/index.mjs:995:7)\r\n[frontend] at async Module.renderSSRHead (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/@unhead/ssr/dist/index.mjs:77:23)\r\n[frontend] [nuxt] [request error] [unhandled] [500] i18next-vue: No Vue instance in context. Make sure to register the i18next-vue plugin using app.use(...).\r\n[frontend] at Module.useTranslation (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/i18next-vue/dist/index.mjs:118:11)\r\n[frontend] at translate (C:\\Users\\ckuka\\VS Code Projects\\ows-events\\frontend\\plugins\\i18n.ts:23:41)\r\n[frontend] at titleTemplate (C:\\Users\\ckuka\\VS Code Projects\\ows-events\\frontend\\pages\\index.vue:43:39)\r\n[frontend] at resolveTitleTemplate (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/@unhead/shared/dist/index.mjs:79:12)\r\n[frontend] at tags:resolve (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/unhead/dist/index.mjs:59:28)\r\n[frontend] at /C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/hookable/dist/index.mjs:48:66\r\n[frontend] at /C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/hookable/dist/index.mjs:48:56\r\n[frontend] at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n[frontend] at async Object.resolveTags (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/unhead/dist/index.mjs:995:7)\r\n[frontend] at async Module.renderSSRHead (/C:/Users/ckuka/VS%20Code%20Projects/ows-events/frontend/node_modules/@unhead/ssr/dist/index.mjs:77:23)\n```\n",[2948,2951,2954,2957,2960],{"name":2949,"color":2950},"enhancement","8DEF37",{"name":2952,"color":2953},"discussion","538de2",{"name":2955,"color":2956},"3.x","29bc7f",{"name":2958,"color":2959},"workaround available","11376d",{"name":2961,"color":2962},"🍰 p2-nice-to-have","0E8A16",21457,"Cannot use a plugin in the titleTemplate function","2023-06-08T20:46:09Z","https://github.com/nuxt/nuxt/issues/21457",0.7237909,{"description":2969,"labels":2970,"number":2971,"owner":2877,"repository":2877,"state":2890,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Describe the feature\n\nIt should be described in the docs how to use the [vscode extension for vitest](https://github.com/vitest-dev/vscode) (and similarily the one for jest) with nuxt testing.\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://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[],14969,"Add support for vscode vitest extension","2025-05-12T19:18:59Z","https://github.com/nuxt/nuxt/issues/14969",0.7238206,{"description":2977,"labels":2978,"number":2981,"owner":2877,"repository":2940,"state":2890,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Describe the feature\n\nThis might sound funny, but I am currently opening `nuxt.com` like 50 times a day, mostly to get a docs link to something I want to send to somebody/post somewhere for reference. And I always have to click on \"Docs\" before accessing the input field for the search. \r\n\r\nAn easy fix would be to also add the search field to the `nuxt.com/` home page.\r\n\r\nAs the website repo is not yet open source, I cannot propose a PR.\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://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2979],{"name":2949,"color":2980},"1ad6ff",1225,"[Docs] Add the docs search field to the nuxt.com homepage","2023-10-10T14:45:11Z","https://github.com/nuxt/nuxt.com/issues/1225",0.7245066,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ftlCL0HIYNkyfu9wkvQEVUZ9EMAN98CUq2Tbaw2GfzUU":-1},"/nuxt/nuxt.com/728"]