\n\nHowever, in v4, only the base interface is considered:\n\n\u003Cimg width=\"305\" height=\"121\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0d52e563-e507-4f53-9e34-a51086879f76\" />\n\n### Additional context\n\nThe v4 projects are using the new default tsconfig\n```json\n{\n // https://nuxt.com/docs/guide/concepts/typescript\n \"files\": [],\n \"references\": [\n {\n \"path\": \"./.nuxt/tsconfig.app.json\"\n },\n {\n \"path\": \"./.nuxt/tsconfig.server.json\"\n },\n {\n \"path\": \"./.nuxt/tsconfig.shared.json\"\n },\n {\n \"path\": \"./.nuxt/tsconfig.node.json\"\n }\n ]\n}\n```\n\n### Logs\n\n```shell-script\n\n```",[3019,3022],{"name":3020,"color":3021},"pending triage","E99695",{"name":3023,"color":3024},"possible regression","B90A42",32727,"nuxt","open","Type augmentations broken in v4","2025-07-23T00:55:36Z","https://github.com/nuxt/nuxt/issues/32727",0.72618806,{"description":3033,"labels":3034,"number":3037,"owner":3026,"repository":3038,"state":3027,"title":3039,"updated_at":3040,"url":3041,"score":3042},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-912ubv\n\nrun `pnpm test:browser` and check the components directory for Foo.vue and Foo.test.ts\n\n### Describe the bug\n\nI'm following steps 1 and 2 from the [setup](https://nuxt.com/docs/getting-started/testing#setup), but when running `vitest` in browser mode I get the following error in the browser UI:\n\nReferenceError: process is not defined\n❯ /node_modules/.pnpm/vite@5.4.8_@types+node@22.7.5_terser@5.34.1/node_modules/vite/dist/client/env.mjs:12:519\n\nCould that be because `process` is in fact referenced inside https://github.com/nuxt/test-utils/blob/main/src/config.ts, when I'm running the test runner under a browser environment, and not in Node? If so, how can I configure vitest to run in browser mode under Nuxt environment?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3035],{"name":3020,"color":3036},"5D08F5",984,"test-utils","Unable to use with Vitest in browser mode","2024-10-24T07:47:14Z","https://github.com/nuxt/test-utils/issues/984",0.73330814,{"description":3044,"labels":3045,"number":3046,"owner":3026,"repository":3047,"state":3048,"title":3049,"updated_at":3050,"url":3051,"score":3052},"https://www.figma.com/file/OLlmzoVQ7FSBh4FJJORNpl/%F0%9F%96%A5---nuxt.com?node-id=5246%3A48502",[],543,"nuxt.com","closed","[Community] Nuxters page integration `/community/nuxters`","2023-02-15T12:32:30Z","https://github.com/nuxt/nuxt.com/issues/543",0.46357837,{"description":3054,"labels":3055,"number":3059,"owner":3026,"repository":3038,"state":3048,"title":3060,"updated_at":3061,"url":3062,"score":3063},"I have a custom composable (`useConsent`), which I am trying to mock. \r\nI'm importing the composable like so:\r\n\r\n`import { useConsent, useHead } from '#imports'`.\r\n\r\nThe import is recognized in `packages/vitest-environment-nuxt/src/modules/mock.ts`:\r\n```\r\n{\r\n name: \"default\",\r\n as: \"useConsent\",\r\n from: \"[...]/src/runtime/composables/useConsent.ts\",\r\n priority: undefined,\r\n}\r\n```\r\n\r\nEven though the import is recognized and no `\"Cannot find import to mock\"` error is thrown, the import is not mocked.\r\nIn the same file I am mocking `useHead`, that one is mocked without any issues.\r\n\r\nUsing `nuxt-vitest@0.8.4`\r\n",[3056],{"name":3057,"color":3058},"vitest-environment","b60205",524,"custom composable without function name not mocked with `mockNuxtImport`","2023-12-02T00:17:13Z","https://github.com/nuxt/test-utils/issues/524",0.6876495,{"description":3065,"labels":3066,"number":3070,"owner":3026,"repository":3047,"state":3048,"title":3071,"updated_at":3072,"url":3073,"score":3074},"https://vueuse.org/core/useInfiniteScroll/",[3067],{"name":3068,"color":3069},"enhancement","1ad6ff",529,"[Community] Infinite scroll on repositories list","2023-02-15T12:31:29Z","https://github.com/nuxt/nuxt.com/issues/529",0.6982896,{"description":3076,"labels":3077,"number":3070,"owner":3026,"repository":3038,"state":3048,"title":3079,"updated_at":3080,"url":3081,"score":3074},"Hello,\r\n\r\nWhen i want to use the MountSuspended helper, I've got this error.\r\n\u003Cimg width=\"829\" alt=\"image\" src=\"https://github.com/danielroe/nuxt-vitest/assets/14348168/18027eac-ccd4-4882-bdbb-6e0aac8b269c\">\r\n\r\nHere my test code and vitest config \r\n\u003Cimg width=\"1164\" alt=\"image\" src=\"https://github.com/danielroe/nuxt-vitest/assets/14348168/81855b82-2987-4f7f-a388-397780d04d57\">\r\n\r\nI don't know if i do something wrong or if it's an issue, so i need your help please !\r\n\r\nThanks a lot",[3078],{"name":3057,"color":3058},"Timeout on mountSuspended helper","2023-12-02T00:22:10Z","https://github.com/nuxt/test-utils/issues/529",{"description":3083,"labels":3084,"number":3086,"owner":3026,"repository":3047,"state":3048,"title":3087,"updated_at":3088,"url":3089,"score":3090},"We can create a component for this that will allow us to use it on modules and agencies",[3085],{"name":3068,"color":3069},1195,"[Agencies]: add not found layout if no result","2023-02-15T12:31:15Z","https://github.com/nuxt/nuxt.com/issues/1195",0.70677656,{"description":3092,"labels":3093,"number":3099,"owner":3026,"repository":3026,"state":3048,"title":3100,"updated_at":3101,"url":3102,"score":3103},"### Describe the feature\n\nHey there! I'm really excited about the new `typedPages` feature. Great work on that one!\r\n\r\nI would like to create composable, for example a `useGetAppLocation`, that essentially returns a resolved url while adding a param that every url in my app needs. Example:\r\n\r\n```ts\r\n// props must be any because we don't have a type for it :/\r\nexport const useGetAppLocation = (props: any) => {\r\n\tconst router = useRouter()\r\n\tconst currentSpaceStore = useCurrentSpaceStore()\r\n\r\n\treturn router.resolve({\r\n\t\t...props,\r\n\t\tparams: {\r\n\t\t\t...props.params,\r\n\t\t\tspaceKey: currentSpaceStore.currentSpaceKey\r\n\t\t}\r\n\t})\r\n}\r\n```\r\n\r\nI would like to type this function, but as far as I can see nuxt doesn't export any types to do so. The `router.resolve()` uses `RouteNameMap`, `RouteLocationAsRelativeTyped`, `RouteLocationResolvedTyped ` and so on.\r\n\r\nIdeally, these types could be used in an application.\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).",[3094,3096],{"name":3068,"color":3095},"8DEF37",{"name":3097,"color":3098},"3.x","29bc7f",21032,"`experimental.typedPages`: Export types to make usable in application","2023-05-24T12:19:35Z","https://github.com/nuxt/nuxt/issues/21032",0.7073748,{"description":3105,"labels":3106,"number":3112,"owner":3026,"repository":3026,"state":3048,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Describe the feature\n\nCurrently `component.d.ts` file is generated based on the `filePath` and `export` properties passed to `addComponent` function as defined [here](https://github.com/nuxt/nuxt/blob/main/packages/nuxt/src/components/templates.ts#L105-L122). \r\n\r\nThere are cases where component source and types are defined separately. This is possible to workaround if you have control over the components but this not always the case for module authors.\r\n\r\nI suggest something like:\r\n```ts\r\naddComponent({\r\n name: 'MyComponent',\r\n filePath: 'lib/components/my-component',\r\n export: 'default',\r\n // If `typings` is not defined, it falls back to current implementation.\r\n typings: {\r\n filePath: 'lib/types',\r\n export: 'MyComponent'\r\n }\r\n})\r\n```\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).",[3107,3108,3111],{"name":3068,"color":3095},{"name":3109,"color":3110},"discussion","538de2",{"name":3097,"color":3098},19521,"feat(kit): Allow specifying types for `addComponent`","2023-04-04T17:13:58Z","https://github.com/nuxt/nuxt/issues/19521",0.7102932,{"description":3118,"labels":3119,"number":3128,"owner":3026,"repository":3026,"state":3048,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Describe the feature\n\nSeveral composable functions ( `useState`, `useFetch`, `useAsyncData`, `useLazyAsyncData`, `useLazyFetch`) provide auto-key generation that is unique to the file name and line number of the instance of function call. However, this makes it impossible to create your own wrappers around these functions, because then the auto-generated key will always be the same for any wrapper-function call.\r\n\r\n```ts\r\n// composables/useAsyncSpecifiedData.ts\r\nexport function useAsyncSpecifiedData(params) {\r\n\t// ... do some work\r\n\tconst handler = createHandler( params )\r\n\tconst options = createOptions( params )\r\n\treturn useAsyncData(handler, options) // \u003C- the unique key always generated exactly for this file+line\r\n}\r\n```\r\nI would like to have oportynity to somehow expand keyed functions with myown\r\nhttps://github.com/nuxt/framework/blob/51bc6e44fef6e4a249946ba910a497089b089a64/packages/vite/src/plugins/composable-keys.ts#L15-L17\r\n\r\nSo that nuxt will generates a unique key directly for the wrapper function call, which will be passed down in `useAsyncData`. Since it is work for `useLazyAsyncData`\r\nhttps://github.com/nuxt/framework/blob/51bc6e44fef6e4a249946ba910a497089b089a64/packages/nuxt/src/app/composables/asyncData.ts#L263-L274\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://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3120,3121,3124,3125],{"name":3068,"color":3095},{"name":3122,"color":3123},"good first issue","fbca04",{"name":3097,"color":3098},{"name":3126,"color":3127},"🍰 p2-nice-to-have","0E8A16",12369,"Ability to add your own keyed functions ","2023-03-07T21:06:18Z","https://github.com/nuxt/nuxt/issues/12369",0.7170554,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRI4HklumeWPhrthD0QAn6UAa94QX8X3zWTEnMMqktck":-1},"/nuxt/test-utils/543"]