` component, but it doesn’t work.\n",[],365,"nuxt","icon","open","Is there a way to change the viewBox attribute of an SVG element?","2025-03-05T19:09:39Z","https://github.com/nuxt/icon/issues/365",0.779297,{"description":3029,"labels":3030,"number":3034,"owner":3021,"repository":3035,"state":3023,"title":3036,"updated_at":3037,"url":3038,"score":3039},"# Affected page\r\nhttps://nuxt.com/deploy/aws-amplify\r\n\r\n# Description\r\nThe documentation states that the integration of a Nuxt 3 app with AWS Amplify requires zero configuration. But that is not the case and I'll explain why.\r\n\r\nThe default build config that AWS Amplify generates is this:\r\n```yaml\r\nversion: 1\r\nfrontend:\r\n phases:\r\n preBuild:\r\n commands:\r\n - nvm use 18\r\n - corepack enable\r\n - npx --yes nypm i\r\n build:\r\n commands:\r\n - yarn run build\r\n artifacts:\r\n baseDirectory: .amplify-hosting\r\n files:\r\n - '**/*'\r\n```\r\n\r\nHowever, Nuxt's build (and generate) command generates an `.output` directory that contains the app's contents ready to be served.\r\n\r\nHence, the `baseDirectory` property in Amplify's build config will need to be updated to `.output/public`. Hence, Nuxt's integration with AWS Amplify isn't zero config.\r\n\r\nHappy to open a PR.\r\n\r\nP.S: [Nitro's docs](https://nitro.unjs.io/deploy/providers/aws-amplify) might be misleading as well.\r\n",[3031],{"name":3032,"color":3033},"question","ff1ab2",1439,"nuxt.com","Improve setup steps on deploying Nuxt app to AWS Amplify on docs","2023-12-15T09:16:42Z","https://github.com/nuxt/nuxt.com/issues/1439",0.7824605,{"description":3041,"labels":3042,"number":3052,"owner":3021,"repository":3053,"state":3054,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### Describe the feature\n\nVitest current version is 2.0.3.\r\n@nuxt/test-utils uses Vitest 1.0.6.\r\n\r\nError:\r\n```\r\nnpm ERR! code ERESOLVE\r\nnpm ERR! ERESOLVE could not resolve\r\nnpm ERR! \r\nnpm ERR! While resolving: @nuxt/test-utils@3.13.1\r\nnpm ERR! Found: vitest@2.0.3\r\nnpm ERR! node_modules/vitest\r\nnpm ERR! dev vitest@\"2.0.3\" from the root project\r\nnpm ERR! \r\nnpm ERR! Could not resolve dependency:\r\nnpm ERR! peerOptional vitest@\"^0.34.6 || ^1.0.0\" from @nuxt/test-utils@3.13.1\r\nnpm ERR! node_modules/@nuxt/test-utils\r\nnpm ERR! dev @nuxt/test-utils@\"3.13.1\" from the root project\r\nnpm ERR! @nuxt/test-utils@\">=3.9.0\" from vitest-environment-nuxt@1.0.0\r\nnpm ERR! node_modules/vitest-environment-nuxt\r\nnpm ERR! vitest-environment-nuxt@\"^1.0.0\" from @nuxt/test-utils@3.13.1\r\nnpm ERR! \r\nnpm ERR! Conflicting peer dependency: vitest@1.6.0\r\nnpm ERR! node_modules/vitest\r\nnpm ERR! peerOptional vitest@\"^0.34.6 || ^1.0.0\" from @nuxt/test-utils@3.13.1\r\nnpm ERR! node_modules/@nuxt/test-utils\r\nnpm ERR! dev @nuxt/test-utils@\"3.13.1\" from the root project\r\nnpm ERR! @nuxt/test-utils@\">=3.9.0\" from vitest-environment-nuxt@1.0.0\r\nnpm ERR! node_modules/vitest-environment-nuxt\r\nnpm ERR! vitest-environment-nuxt@\"^1.0.0\" from @nuxt/test-utils@3.13.1\r\nnpm ERR! \r\nnpm ERR! Fix the upstream dependency conflict, or retry\r\nnpm ERR! this command with --force or --legacy-peer-deps\r\nnpm ERR! to accept an incorrect (and potentially broken) dependency resolution.\r\n```\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).",[3043,3046,3049],{"name":3044,"color":3045},"bug","d73a4a",{"name":3047,"color":3048},"vitest-environment","b60205",{"name":3050,"color":3051},"pending triage","5D08F5",892,"test-utils","closed","Error updating to Vitest 2","2024-07-29T08:50:37Z","https://github.com/nuxt/test-utils/issues/892",0.7049293,{"description":3060,"labels":3061,"number":3068,"owner":3021,"repository":3053,"state":3054,"title":3069,"updated_at":3070,"url":3071,"score":3072},"### Describe the feature\n\n## 🚀 Why This Feature?\r\n\r\nNuxt Test Utils provides a variety of tools for conducting End-to-End (E2E) tests with `playwright` and a chosen test runner (currently `vitest` or `jest`). While this is a valuable capability, I believe it could be enhanced further by integrating support for Cucumber.\r\n\r\nHere's the challenge: to initiate a Nuxt server for E2E tests, you typically invoke the `setup()` method from the `test-utils/e2e` Nuxt package, as documented [here](https://nuxt.com/docs/getting-started/testing#setup-1). In essence, this function determines your test runner and associates specific actions with different hooks (e.g., starting the server in `beforeAll`, closing the connection in `afterAll`, etc.).\r\n\r\nThe issue is that using this method outside of a test runner ecosystem (`jest` or `vitest`) is problematic because it cannot locate the necessary hooks to attach the functions to.\r\n\r\n## 🧠 How to Implement It?\r\n\r\nI propose exposing the various functions called by `setup()` and manually invoking them in the framework of your choice, such as Cucumber. For instance, you could do something like this in TypeScript:\r\n\r\n```typescript\r\n// This is the Before hook of Cucumber\r\nBefore(async function(this: CustomWorld): Promise\u003Cvoid> {\r\n // Create a Playwright Test Context with desired options\r\n const context = createTestContext({});\r\n await startServer(context);\r\n \r\n // Use the Playwright API in Cucumber step definitions\r\n this.page = await createPage(\"/\");\r\n});\r\n```\r\n\r\nI'm unsure if this is already achievable. Regardless, I haven't come across any relevant implementations of `nuxt3` + `playwright` + `cucumber`.\r\n\r\n## 🔍 Reproduction Repository\r\n\r\nYou can test my setup in my [repository](https://github.com/antoinezanardi/werewolves-assistant-web-next/tree/develop) by running the `npm run test:cucumber` command.\r\n\r\nI'd be delighted to assist in building this feature. If it's already possible or implemented differently, I'd appreciate the opportunity to document it in the Nuxt documentation.\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).",[3062,3065],{"name":3063,"color":3064},"documentation","0075ca",{"name":3066,"color":3067},"enhancement","a2eeef",697,"Support E2E tests within Cucumber ecosystem","2024-03-29T09:57:55Z","https://github.com/nuxt/test-utils/issues/697",0.72864765,{"description":3074,"labels":3075,"number":3079,"owner":3021,"repository":3021,"state":3054,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Describe the feature\r\n\r\nUpgrading to Nuxt Bridge was recommended for current apps. There should be clear steps on how to get from there to Nuxt 3. This should especially cover what's in package.json, which isn't covered in the docs even for the Nuxt 2 -> 3 upgrade.\r\n\r\n### Additional information\r\n\r\n- [ ] 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://v3.nuxtjs.org/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3076],{"name":3077,"color":3078},"good first issue","fbca04",15490,"Request: Upgrade instructions from Bridge to Nuxt 3","2025-06-06T09:44:38Z","https://github.com/nuxt/nuxt/issues/15490",0.76130295,{"description":3085,"labels":3086,"number":3089,"owner":3021,"repository":3035,"state":3054,"title":3090,"updated_at":3091,"url":3092,"score":3093},"https://nuxt.com/docs/community/changelog",[3087],{"name":3066,"color":3088},"1ad6ff",1218,"add release notes and changelog","2023-10-10T14:45:09Z","https://github.com/nuxt/nuxt.com/issues/1218",0.7659114,{"labels":3095,"number":3101,"owner":3021,"repository":3021,"state":3054,"title":3102,"updated_at":3103,"url":3104,"score":3105},[3096,3098],{"name":3066,"color":3097},"8DEF37",{"name":3099,"color":3100},"2.x","d4c5f9",10075,"Missing upgrade guide from 1.x to 2.x","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/10075",0.7696087,{"description":3107,"labels":3108,"number":3112,"owner":3021,"repository":3113,"state":3054,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.14.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Version\n\nv2.18.6\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/Yves852/nuxt-ui-commandpalette-hover\n\n### Description\n\nHovering the list of element with the mouse don't show visual effects contrary to [doc example](https://ui.nuxt.com/components/command-palette#usage), It's updated with up/down keys.\r\n\r\nCould be related to [1708](https://github.com/nuxt/ui/issues/1708)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3109],{"name":3110,"color":3111},"duplicate","cfd3d7",2284,"ui","CommandPalette: hover not working","2024-11-13T09:11:36Z","https://github.com/nuxt/ui/issues/2284",0.7789656,{"labels":3119,"number":3120,"owner":3021,"repository":3021,"state":3054,"title":3121,"updated_at":3122,"url":3123,"score":3124},[],13613,"Support firebase regions other than the default","2023-01-19T17:02:41Z","https://github.com/nuxt/nuxt/issues/13613",0.7845987,{"description":3126,"labels":3127,"number":3129,"owner":3021,"repository":3035,"state":3054,"title":3130,"updated_at":3131,"url":3132,"score":3133},"",[3128],{"name":3066,"color":3088},395,"Docs versioning: `/docs/framework/{version}`","2022-04-26T12:02:30Z","https://github.com/nuxt/nuxt.com/issues/395",0.78713787,["Reactive",3135],{},["Set"],["ShallowReactive",3138],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBl9hbR2dxGJ4Xo3L65AV9dqH3Q2nrkLRT1uXxxXRC4g":-1},"/nuxt/nuxt.com/706"]