\n\nI'm also using UModal, UCard elsewhere in the app itself, they do work there.\nSo what do I need to do to get these files parsed my vite/vue/nuxt ui?",[3139],{"name":3140,"color":3141},"question","d876e3",4892,"nuxt","ui","open","Using Nuxt UI in components from a npm package, in Vue","2025-09-05T08:48:22Z","https://github.com/nuxt/ui/issues/4892",0.7176256,{"description":3151,"labels":3152,"number":3153,"owner":3143,"repository":3154,"state":3155,"title":3156,"updated_at":3157,"url":3158,"score":3159},"It would be really good to know why using `@nuxt/test-utils` is more beneficial than using `@vue/test-utils` in a Nuxt project. Despite the obvious point being this package is made specifically for Nuxt, `@vue/test-utils` still works perfectly well in Nuxt projects.\r\n\r\nCould we get some comparison docs (a table maybe) of what `@vue/test-utils` can't do for a Nuxt project, but `@nuxt/test-utils` can?",[],298,"test-utils","closed","@nuxt/test-utils vs @vue/test-utils?","2023-12-02T00:18:11Z","https://github.com/nuxt/test-utils/issues/298",0.44510776,{"description":3161,"labels":3162,"number":3163,"owner":3143,"repository":3154,"state":3155,"title":3164,"updated_at":3165,"url":3166,"score":3167},"Hello everyone,\r\n\r\nI have a few questions about Nuxt test-utils.\r\n\r\nMy situation:\r\n\r\n- I have a Vue.js project with Vue test-utils;\r\n- I have a Nuxt.js project where I would like to add testing;\r\n\r\nI'm looking into different options for libraries to test my Nuxt.js project. Ideally, I would like to have something very similar to Vue test-utils, in order to avoid headaches when working on both projects. Nuxt test-utils seems like an interesting option, but I was wondering what are its advantages compared to just using Vue test-utils? Thanks!",[],296,"Question: Vue test-utils vs Nuxt test-utils","2023-12-02T00:23:09Z","https://github.com/nuxt/test-utils/issues/296",0.5826915,{"description":3161,"labels":3169,"number":3170,"owner":3143,"repository":3154,"state":3155,"title":3164,"updated_at":3171,"url":3172,"score":3167},[],370,"2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/370",{"description":3174,"labels":3175,"number":3182,"owner":3143,"repository":3143,"state":3155,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### What problem does this feature solve?\n\nI cannot find a working solution that let's me use ava or jest to run unit tests that utilize the Vue Test Utils library. Given that both Vue Test Utils and Nuxt appear to hold strong positions within the Vue community, I think it makes sense to ensure that Vue Test Utils can be utilized for both Nuxt universal and Nuxt SPAs\n\n### What does the proposed changes look like?\n\nNuxt should seamlessly let developers run tests with runners like jest or ava while using Vue-test-utils as well as modern ES features (import statements). Importing .vue SFCs from your test files would work fine, using the import statement would work fine, and utilizing Vue Test Util features like shallowMount would work fine.\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/c7972\">#c7972\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3176,3179],{"name":3177,"color":3178},"enhancement","8DEF37",{"name":3180,"color":3181},"2.x","d4c5f9",4115,"Enable Vue-Test-Utils to work with Nuxt","2023-01-22T15:50:48Z","https://github.com/nuxt/nuxt/issues/4115",0.6385043,{"description":3188,"labels":3189,"number":3190,"owner":3143,"repository":3154,"state":3155,"title":3191,"updated_at":3192,"url":3193,"score":3194},"Hi,\r\n\r\nI was trying to integrate @nuxt/test-utils in my Nuxt application in order to test pages.\r\nI already have a bunch of tests written for the components that use @vue/test-utils.\r\n\r\nAfter following the documentation and adding the `@nuxt/test-utils` preset to my jest configuration, all my components tests started failing with the same error:\r\n\r\n```shell\r\n[vue-test-utils]: window is undefined, vue-test-utils needs to be run in a browser environment. \r\n You can run the tests in node using jsdom \r\n See https://vue-test-utils.vuejs.org/guides/#browser-environment for more details.\r\n```\r\n\r\nAny idea how to solve this and be able to use both tools within the same project ?\r\n\r\nThanks!",[],327,"Conflict between @nuxt/test-utils jest preset and @vue/test-utils","2023-12-02T00:23:10Z","https://github.com/nuxt/test-utils/issues/327",0.6559254,{"description":3196,"labels":3197,"number":3204,"owner":3143,"repository":3143,"state":3155,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Describe the feature\r\n\r\nAfter reading [Testing-Get started docs](https://nuxt.com/docs/getting-started/testing#unit-testing) I had confusion on whether I could use the already existing `@vue/test-utils`. I was able to do it after following a guide I found online and it worked just fine.\r\n\r\nI wanted to raise this topic and ask if you think it would be useful to also add a section on how to set this in a new Nuxt 3 project? Was thinking just a basic step-by-step process on how to add `@vue/test-utils`, `vitest` and `happy-dom` and spin up a simple Unit test.\r\n\r\nI know we already have `@nuxt/test-utils` but in some old projects it might be useful to also have a short guide on `@vue/test-utils`. What do you think?\r\n\r\n### Additional information\r\n\r\n- [X] 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://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3198,3201],{"name":3199,"color":3200},"documentation","5319e7",{"name":3202,"color":3203},"3.x","29bc7f",26178,"Docs: Add @vue/test-utils example in Getting started with Unit testing","2024-04-19T14:16:01Z","https://github.com/nuxt/nuxt/issues/26178",0.6642919,{"labels":3210,"number":3215,"owner":3143,"repository":3143,"state":3155,"title":3216,"updated_at":3217,"url":3218,"score":3219},[3211,3214],{"name":3212,"color":3213},"pending triage","E99695",{"name":3180,"color":3181},6852,"Compatibility issue with Nuxt@2.11 and @vue/test-utils","2023-01-22T15:34:48Z","https://github.com/nuxt/nuxt/issues/6852",0.7038783,{"description":3221,"labels":3222,"number":3228,"owner":3143,"repository":3143,"state":3155,"title":3229,"updated_at":3230,"url":3231,"score":3232},"Originally suggested by @Atinux (years ago!) and in nuxt/framework#443 there are common js libraries we built as separated npm packages (mostly in [unjs](https://github.com/unjs). The main idea is to keep the best modularity and easily versioning them and also help the entire js ecosystem by making standalone tools. Using some libraries is common enough that each nuxt project doesn't need to install them one by one for use in end nuxt projects.\r\n\r\nThe idea is that we can re-export them from a single preset of trusted packages that make life easier.\r\n\r\nThis has a disadvantage in that we are making versioning dependent (so if one of these utils has a breaking change entire package needs a major update). Because of this, we cannot directly export them from `@nuxt/kit` (nor is the kit's purpose to provide general utilities but is an SDK for nuxt) and also have to be careful only including useful utils to reduce breaking changes surface.\r\n\r\nAnother aspect is tree-shaking support. Using ESM and `sideEffects: false` we can have good confidence about this still combining server/node dependencies can have unwanted side-effects like extra polyfills and also slower dev time when tree-shaking is not happening or all libs need at least one-time parsing. For this, we can use named subpaths of packages like `@nuxt/stdlib/url` (exporting `ufo` utils) that also make naming more semantic (comparing to funny package names)\r\n\r\nUsage example:\r\n\r\n```js\r\nimport { log } from '@nuxt/stdlib/console'\r\nimport { withBase } from '@nuxt/stdlib/url'\r\n```\r\n\r\nA suggestion for included packages in stdlib subpaths:\r\n\r\n- `/url`: [`ufo`](https://github.com/unjs/ufo)\r\n- `/object`: [defu](https://github.com/unjs/defu) and [destr](https://github.com/unjs/destr)\r\n- `/console`: [consola](https://github.com/unjs/consola/)\r\n- `/fetch`: [ohmyfetch](https://github.com/unjs/ohmyfetch)\r\n- `/http`: [h3](https://github.com/unjs/h3), [is-https](https://github.com/unjs/is-https), [requrl](https://github.com/unjs/requrl)\r\n- `/string`: [scule](https://github.com/unjs/scule)\r\n- `/esm`: [mlly](https://github.com/unjs/mlly)\r\n- `/env`: [stdenv](https://github.com/unjs/std-env)\r\n- `/promise`: [items-promise](https://github.com/unjs/items-promise), [p-debounce](https://www.npmjs.com/package/p-debounce), [...promise-fun](https://github.com/sindresorhus/promise-fun)\r\n\r\nWe can also dedicate a section in documentation to `stdlib` and for each sub-path, auto-generate docs from their TSDocs using [untyped](https://github.com/unjs/untyped) (Related: More packages listing in [/internals/contrib](https://v3.nuxtjs.org/internals/contrib))\r\n",[3223,3224,3227],{"name":3177,"color":3178},{"name":3225,"color":3226},"discussion","538de2",{"name":3202,"color":3203},11827,"`@nuxt/stdlib`","2023-01-19T15:44:50Z","https://github.com/nuxt/nuxt/issues/11827",0.71348536,{"description":3234,"labels":3235,"number":3237,"owner":3143,"repository":3143,"state":3155,"title":3238,"updated_at":3239,"url":3240,"score":3241},"Hi, I am a beginner using nuxt. I using Vue Flow in the Nuxt project, loading \"@ vue flow/core/dist/style. css\" does not work. How to configure Vue packages(Vue Flow) in the Nuxt project? ",[3236],{"name":3212,"color":3213},32582,"Vue flow cannot work in nuxt","2025-07-11T09:05:35Z","https://github.com/nuxt/nuxt/issues/32582",0.7139167,["Reactive",3243],{},["Set"],["ShallowReactive",3246],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fp4JFTm_UQHD_oZivhlZLI660Hr6Wg2oJTf7nQ0bJR3g":-1},"/nuxt/icon/298"]