\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[1984,1987],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"triage","ffffff",2713,"nuxt","ui","open","UInput Component Lacks Proper Handling of compositionstart and compositionend","2024-11-21T06:40:46Z","https://github.com/nuxt/ui/issues/2713",0.76344264,{"description":1999,"labels":2000,"number":2002,"owner":1991,"repository":2003,"state":2004,"title":2005,"updated_at":2006,"url":2007,"score":2008},"I've upgraded `@nuxt/fonts` to `v0.10.0` and after running `npm run dev` receiving the following errors:\n\n```\n[10:08:40 PM] ERROR Could not resolve font face for Segoe UI from adobe provider. Cannot read properties of undefined (reading 'resolveFont')\n[10:08:40 PM] ERROR Could not resolve font face for SFMono-Regular from adobe provider. Cannot read properties of undefined (reading 'resolveFont')\n[10:08:40 PM] ERROR Could not resolve font face for Inter from adobe provider. Cannot read properties of undefined (reading 'resolveFont')\n```\n\nI've tried to set `adobe: false` in the config, but still getting these errors. I'm using `Inter` font only: `font-family: \"Inter\", sans-serif;`\n\n\n",[2001],{"name":1985,"color":1986},328,"fonts","closed","CLI error after upgrading to v0.10.0","2024-10-08T21:31:44Z","https://github.com/nuxt/fonts/issues/328",0.7367689,{"description":2010,"labels":2011,"number":2002,"owner":1991,"repository":2012,"state":2004,"title":2013,"updated_at":2014,"url":2015,"score":2008},"I encountered an error when running npm run build in my Nuxt 3 project. The error message states:\n\n**ERROR Nuxt module should be a function: nuxt-icon**\n\nThis issue happens while trying to build the project, even after installing the latest version of nuxt-icon. The versions of the dependencies in my project are as follows:\n\n**Nuxt Version: 3.14.159\nNode Version: v18.20.4\nnuxt-icon Version: ^0.5.0\nCLI Version: 3.15.0\nNitro Version: 2.10.4**\n\nI have tried reinstalling the nuxt-icon module and performing a cleanup using npx nuxi cleanup, but the issue persists.\n\nSteps to reproduce:\n\nSet up a Nuxt 3 project.\nInstall nuxt-icon (version ^0.5.0).\nRun npm run build.\n\nThe error occurs.\nExpected behavior: The build process should complete successfully without any errors related to the nuxt-icon module.\n\nAdditional context:\n\nI am using yarn as the package manager.\nI have also checked that my nuxt.config.ts is properly configured to use nuxt-icon.\nHow to resolve:\n\nI have tried solutions such as cleaning up the cache and reinstalling dependencies, but the issue persists.\nThe issue seems to be related to the nuxt-icon module not being recognized as a function by Nuxt.\n\n\n",[],"icon","Nuxt module should be a function: nuxt-icon","2024-12-22T11:07:06Z","https://github.com/nuxt/icon/issues/328",{"description":2017,"labels":2018,"number":2025,"owner":1991,"repository":1992,"state":2004,"title":2026,"updated_at":2027,"url":2028,"score":2029},"### Description\n\nI can see there was some changes [here](https://github.com/nuxt/ui/pull/3123) which is great.\n\nI'm just wondering why the 'help' property was excluded from these additions?\n\nThank you!",[2019,2022],{"name":2020,"color":2021},"question","d876e3",{"name":2023,"color":2024},"v3","49DCB8",3685,"Was UFormField 'help' property excluded from the aria-describedby update for any specific reason?","2025-03-26T12:47:39Z","https://github.com/nuxt/ui/issues/3685",0.73961735,{"description":2031,"labels":2032,"number":2033,"owner":1991,"repository":2034,"state":2004,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### Describe the feature\n\nHaving documentation available offline is important for people working while travelling (e.g. train) or having an unreliable internet connection for other reasons. Vuetify and Quasar have hooked in service worker to allow browsing their docs offline which is very helpful in these scenarios.\r\n\r\nIt would be great if the Nuxt documentation could also register a service worker which would allow offline viewing.\n\n### Additional information\n\n- [ ] 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).",[],1286,"nuxt.com","Make documentation work offline","2023-10-10T14:44:47Z","https://github.com/nuxt/nuxt.com/issues/1286",0.74298304,{"description":2040,"labels":2041,"number":2045,"owner":1991,"repository":1991,"state":2004,"title":2046,"updated_at":2047,"url":2048,"score":2049},"I don't have time to make push request 😢\r\n\r\nI based in:\r\n- https://github.com/nuxt/nuxt.js/blob/dev/packages/webpack/src/config/base.js\r\n- https://github.com/TypeStrong/ts-loader/blob/master/examples/thread-loader/webpack.config.js\r\n\r\n```\r\n/* eslint-disable @typescript-eslint/camelcase,@typescript-eslint/no-var-requires */\r\nconst isProduction = process.env.NODE_ENV === 'production';\r\nconst ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');\r\nconst cwd = process.cwd();\r\nconst tsConfig = path.resolve(cwd, 'tsconfig.json');\r\nconst tsChecker = new ForkTsCheckerWebpackPlugin({\r\n tsconfig: tsConfig,\r\n checkSyntacticErrors: isProduction,\r\n formatter: 'codeframe',\r\n vue: true\r\n});\r\nconst findRule = (config, test) => config.module.rules.find(rule => rule.test.toString() === test.toString());\r\n\r\nmodule.exports = {\r\n build: {\r\n loaders: {\r\n ts: {\r\n configFile: tsConfig,\r\n transpileOnly: true,\r\n appendTsSuffixTo: [/\\.vue$/],\r\n happyPackMode: isProduction\r\n },\r\n tsx: {\r\n configFile: tsConfig,\r\n transpileOnly: true,\r\n appendTsxSuffixTo: [/\\.vue$/],\r\n happyPackMode: isProduction\r\n }\r\n },\r\n extend(config, ctx) {\r\n // Run ESLint on save in ts and tsx too\r\n if (ctx.isDev && ctx.isClient) {\r\n config.module.rules.push({\r\n enforce: 'pre',\r\n test: /\\.(js|vue|ts|tsx)$/,\r\n loader: 'eslint-loader',\r\n exclude: /(node_modules)/\r\n });\r\n }\r\n\r\n // Add tsChecker to Webpack\r\n config.plugins.push(tsChecker);\r\n\r\n // Add tsChecker to Webpack\r\n config.plugins.push(tsChecker);\r\n\r\n if (!ctx.isDev) {\r\n // Find the rule for Typescript by regex\r\n const tsRule = findRule(config, '/\\\\.ts$/i');\r\n tsRule.use.unshift('thread-loader');\r\n\r\n // Find the rule for Typescript TSX by regex\r\n const tsxRule = findRule(config, '/\\\\.tsx$/i');\r\n tsxRule.use.unshift('thread-loader');\r\n }\r\n }\r\n },\r\n};\r\n```\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8841\">#c8841\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2042],{"name":2043,"color":2044},"2.x","d4c5f9",5248,"[Feature] TsChecker and Thread-loader in Typescript and TSX","2023-01-18T20:10:47Z","https://github.com/nuxt/nuxt/issues/5248",0.7545837,{"description":2051,"labels":2052,"number":2055,"owner":1991,"repository":2034,"state":2004,"title":2056,"updated_at":2057,"url":2058,"score":2059},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2053],{"name":1985,"color":2054},"ff281a",496,"[Milkdown] On serialize, component props should keep their current format `inline` or `yaml`","2023-06-06T12:14:53Z","https://github.com/nuxt/nuxt.com/issues/496",0.75611186,{"description":2061,"labels":2062,"number":2055,"owner":1991,"repository":2066,"state":2004,"title":2067,"updated_at":2068,"url":2069,"score":2059},"",[2063],{"name":2064,"color":2065},"vitest-environment","b60205","test-utils","documentation/examples","2023-12-02T22:52:29Z","https://github.com/nuxt/test-utils/issues/496",{"description":2071,"labels":2072,"number":2077,"owner":1991,"repository":2003,"state":2004,"title":2078,"updated_at":2079,"url":2080,"score":2081},"at the moment redeploys on cloud providers with `experimental.buildCache` result in font files not being included in published site\r\n\r\n",[2073,2074],{"name":1985,"color":1986},{"name":2075,"color":2076},"good first issue","7057ff",266,"support for nuxt `experimental.buildCache`","2024-09-23T14:18:03Z","https://github.com/nuxt/fonts/issues/266",0.7570621,{"description":2083,"labels":2084,"number":2091,"owner":1991,"repository":1991,"state":2004,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### Describe the feature\n\n## The problem\r\n\r\nUses that need to use interceptors or anything else on `useFetch()` require to:\r\n\r\na. Create a new composable `useCustomFetch()` with the new functionality.\r\nb. Create a new compasable with `$fetch` and add the new functionality with the old.\r\nc. Modify the `useFetch()` on each call in every part of the application.\r\n\r\nAll of these scenarios could be fixed by offering the user a way to modify the `useFetch()` function _before_ its given into userland. \r\n\r\n## Solution\r\n\r\nThis could be accomplished easily by allowing the user to _replace_ the `useFetch()` composable with it' own and receive the original object. Each callback registered would be executed without order guarantee.\r\n\r\n```js\r\n// /composables/useFetch.js\r\n\r\nexport default () => {\r\n return useFetch().global(fetch => {\r\n // ...\r\n })\r\n}\r\n```\r\n\r\nThis approach fixes four things:\r\n\r\n- Doesn't replaces `useFetch()`, it extends it.\r\n- Users that already use `useFetch.js` can still use it as always.\r\n- Users that already use `useCustomFetch.js` can still use it as always.\r\n- Remove the `WARN Duplicated imports \"useFetch\", the one from \"#app\" has been ignored`\n\n### Additional information\n\n- [ ] 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).",[2085,2088],{"name":2086,"color":2087},"3.x","29bc7f",{"name":2089,"color":2090},"pending triage","E99695",22778,"Allow to modify global useFetch","2023-08-24T08:25:40Z","https://github.com/nuxt/nuxt/issues/22778",0.7593624,["Reactive",2097],{},["Set"],["ShallowReactive",2100],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"nMBEw_lpEMl3WPrUwhNWgau6v-aU_PUbRKvYTeEZghE":-1},"/nuxt/test-utils/667"]