\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2867,2870],{"name":2868,"color":2869},"bug","d73a4a",{"name":2871,"color":2872},"triage","ffffff",3583,"nuxt","ui","open","Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.6932404,{"labels":2882,"number":2889,"owner":2874,"repository":2874,"state":2890,"title":2891,"updated_at":2892,"url":2893,"score":2894},[2883,2886],{"name":2884,"color":2885},"3.x","29bc7f",{"name":2887,"color":2888},"pending triage","E99695",13624,"closed","Rollup failed to resolve import \"#_config\" from “paths.mjs”","2023-01-19T17:02:42Z","https://github.com/nuxt/nuxt/issues/13624",0.67615885,{"description":2896,"labels":2897,"number":2901,"owner":2874,"repository":2902,"state":2890,"title":2903,"updated_at":2904,"url":2905,"score":2906},"Hello,\r\n\r\nI'v been trying to use msw along with this module in order to mock requests. However, any component using $fetch or useFetch raises a FetchError when mounting.\r\nIs there anything I've been missing here? I know the msw examples using react polyfill the fetch function, but I don't know how to do it in a nuxt environment.\r\n\r\n```\r\n// app.nuxt.test.ts\r\nimport { test } from 'vitest'\r\nimport app from './app.vue'\r\nimport { mount } from '@vue/test-utils'\r\n\r\ntest('my test', () => {\r\n // setup({ server: true })\r\n // global.fetch = fetch\r\n // globalThis.fetch = fetch\r\n // await mount(app)\r\n mount(app)\r\n})\r\n```\r\n\r\n```\r\n// app.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxtWelcome />\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nconst test = await $fetch('https://google.com')\r\n\u003C/script>\r\n```\r\n\r\n\r\n\r\n",[2898],{"name":2899,"color":2900},"vitest-environment","b60205",557,"test-utils","_fetch is not a function","2023-12-02T00:22:09Z","https://github.com/nuxt/test-utils/issues/557",0.6781918,{"description":2908,"labels":2909,"number":2920,"owner":2874,"repository":2874,"state":2890,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.6.0`\r\n- Nuxt Version: `3.1.1`\r\n- Nitro Version: `2.1.1`\r\n- Package Manager: `pnpm@7.11.0`\r\n- Builder: `vite`\r\n- User Config: `alias`, `extends`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-c1amq4?file=some-subdomain/nuxt.config.ts\r\n\r\n### Describe the bug\r\n\r\nThere are a few subfolders. Each of them contains the same set of components\r\nAnd app should extend some particular folder based on flag set in env\r\n\r\nimport { dynamicSubfolderName } from './env'\r\nexport default defineNuxtConfig({\r\n extends: [`./${dynamicSubfolderName}`]\r\n})\r\n\r\nIn my case there 2 folders. Both contain Logo.vue and both contain a logo.svg in /public/img.\r\n\r\nWhen I run app in dev mode everything works fine. But when run build command I receive an error regarding impossibility to resolve import\r\n\r\n### Additional context\r\n\r\nPutting anything with name logo.svg into root /public folder solves the issue\r\nMaking path dynamic `\u003Cimg :src=\"`${'/img/logo.svg'}`\" >` solves the issue\r\n\r\n### Logs\r\n\r\n```shell-script\r\n[vite]: Rollup failed to resolve import \"/img/logo.svg\" from \"/home/projects/nuxt-starter-c1amq4/some-subdomain/components/Logo.vue\".\r\nThis is most likely unintended because it can break your application at runtime.\r\nIf you do want to externalize this module explicitly add it to\r\n`build.rollupOptions.external`\r\n\r\n ERROR [vite]: Rollup failed to resolve import \"/img/logo.svg\" from \"/home/projects/nuxt-starter-c1amq4/some-subdomain/components/Logo.vue\".\r\nThis is most likely unintended because it can break your application at runtime.\r\nIf you do want to externalize this module explicitly add it to\r\n`build.rollupOptions.external`\r\n\r\n This is most likely unintended because it can break your application at runtime.\r\n If you do want to externalize this module explicitly add it to\r\n `build.rollupOptions.external`\r\n at onRollupWarning (file://node_modules/vite/dist/node/chunks/dep-3007b26d.js:44820:19)\r\n at onwarn (file://node_modules/vite/dist/node/chunks/dep-3007b26d.js:44590:13)\r\n at Object.eval [as onwarn] (file://node_modules/rollup/dist/es/shared/rollup.js:24668:13)\r\n at ModuleLoader.handleInvalidResolvedId (file://node_modules/rollup/dist/es/shared/rollup.js:23352:26)\r\n at eval (file://node_modules/rollup/dist/es/shared/rollup.js:23312:26)\r\n```\r\n",[2910,2911,2914,2917],{"name":2884,"color":2885},{"name":2912,"color":2913},"vite","3574D1",{"name":2915,"color":2916},"🔨 p3-minor","FBCA04",{"name":2918,"color":2919},"layers","006B75",18920," Rollup failed to resolve import image from `extends` folders","2023-05-18T14:10:14Z","https://github.com/nuxt/nuxt/issues/18920",0.68568,{"labels":2926,"number":2929,"owner":2874,"repository":2874,"state":2890,"title":2930,"updated_at":2931,"url":2932,"score":2933},[2927,2928],{"name":2884,"color":2885},{"name":2887,"color":2888},14949,"Failed to resolve component in pages ","2023-01-19T17:42:57Z","https://github.com/nuxt/nuxt/issues/14949",0.68610144,{"labels":2935,"number":2944,"owner":2874,"repository":2874,"state":2890,"title":2945,"updated_at":2946,"url":2947,"score":2948},[2936,2937,2938,2941],{"name":2884,"color":2885},{"name":2912,"color":2913},{"name":2939,"color":2940},"upstream","E8A36D",{"name":2942,"color":2943},"upstream-bug","B60205",13494,"Build failed canot resolve public image","2024-06-15T21:31:12Z","https://github.com/nuxt/nuxt/issues/13494",0.6861793,{"description":2950,"labels":2951,"number":2954,"owner":2874,"repository":2874,"state":2890,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Environment\n\n```\r\n[11:21:41 AM] RootDir: C:/code/bad-imports\r\n[11:21:42 AM] Nuxt project info: \r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v16.19.1\r\n- Nuxt Version: 3.6.4\r\n- Nitro Version: 2.5.2\r\n- Package Manager: npm@8.19.3\r\n- Builder: vite\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\n\n### Reproduction\n\nhttps://github.com/joel-wenzel/bad-imports\r\n\r\n1. Clone repo\r\n2. Open app.vue\r\n3. Hit ctrl+space on the HelloWorld component to bring up the import suggestion\r\n4. Notice the invalid absolute path suggestion of `pages/..` instead of `./pages/..`\r\n\r\n\r\nIf you delete the nuxt tsconfig it then properly suggests a relative path\n\n### Describe the bug\n\nSince somewhere around the 3.6.0 release the import path suggestions in vs code do not seem to be valid in most cases. \r\n\r\n\r\nIn the above image it is suggesting `pages/hello/HelloWorld.vue`. At runtime this fails with \r\n```\r\n[11:25:05 AM] ERROR Failed to resolve import \"pages/hello/HelloWorld.vue\" from \"app.vue\". Does the file exist?\r\n```\r\n\r\nPre 3.6.0 it would suggest `./pages/hello/HelloWorld.vue` which would be valid.\n\n### Additional context\n\nI believe some changes were done to the `.nuxt/tsconfig.json` that are causing the issue. Namely the path aliases now use an absolute path instead of relative ( I think that was done to remove some of the issues around vue 3.3 external prop type references ).\n\n### Logs\n\n_No response_",[2952,2953],{"name":2884,"color":2885},{"name":2887,"color":2888},22228,"Bad import path suggestions since 3.6.0","2023-07-19T21:15:53Z","https://github.com/nuxt/nuxt/issues/22228",0.68778235,{"description":2960,"labels":2961,"number":2966,"owner":2874,"repository":2874,"state":2890,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v21.2.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: devtools, components\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nimport an external component library on app.vue in the nuxt scaffold app and get error:\r\n`[vite-node] [ERR_LOAD_URL] @someOrg/someLib/index.js` \n\n### Describe the bug\n\nWhen using an external organization scoped package it fails to resolve the path at build time with error:\r\n```\r\nERROR Pre-transform error: Failed to resolve import \"@someOrg/someLib/index.js\" from \"app.vue\". Does the file exist?\r\n```\r\nI've tried removing the scope locally and the import works after, i.e. `import { AppButton } from \"someOrg/someLib/index.js\"\";`\r\n\r\nThis happens after upgrading to version 3.9.0, and was not happening with version 3.8.2\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2962,2963,2964],{"name":2884,"color":2885},{"name":2887,"color":2888},{"name":2965,"color":2916},"needs reproduction",25055,"[nuxt 3.9] build failed when importing components from npm package","2024-01-05T20:36:38Z","https://github.com/nuxt/nuxt/issues/25055",0.68915707,{"description":2972,"labels":2973,"number":2974,"owner":2874,"repository":2975,"state":2890,"title":2976,"updated_at":2977,"url":2978,"score":2979},"[Pretty sure this is where a \"rounded-xl\" belongs](https://github.com/nuxt/nuxt.com/blob/b95197b97fc1acbe3582f95589856e9c97fef703/components/home/HomeSectionFeatures.vue#L22), I don't use Vue nor Nuxt so I have no idea how to navigate the codebase & I don't want to make a PR which is potentially incapable of building (too lazy to set up and test change)\n\nWhat it should look like:\n\n\nWhat it actually looks like:\n\n\nAdding a \"rounded-xl\" tailwind class to the sub-div (selected in this screenshot) fixes this and makes it look (presumably) as intended ([as the first screenshot shows](https://github.com/user-attachments/assets/731610cf-9cf9-464f-bf6f-0daff32e8fc4))\n\n",[],1679,"nuxt.com","Presumably unintentional dark edges on corners of card","2024-10-13T10:45:20Z","https://github.com/nuxt/nuxt.com/issues/1679",0.68955153,{"description":2981,"labels":2982,"number":2985,"owner":2874,"repository":2874,"state":2890,"title":2986,"updated_at":2987,"url":2988,"score":2989},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.0\r\n- Nitro Version: 2.6.1\r\n- Package Manager: pnpm@8.6.3\r\n- Builder: -\r\n- User Config: css, runtimeConfig, modules, components, API_URL\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.8.0, @pinia/nuxt@0.4.11\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/github/s1kebeats/s1kebeats_client/issue\r\n\r\n### Describe the bug\r\n\r\n[AppLogo](https://github.com/s1kebeats/s1kebeats_client/blob/dev/components/ui/AppLogo/AppLogo.vue) component import works in [form.vue](https://github.com/s1kebeats/s1kebeats_client/blob/dev/layouts/form.vue), but doesn't work in [AppHeader](https://github.com/s1kebeats/s1kebeats_client/blob/dev/components/modules/AppHeader/AppHeader.vue). Imports are absolutely identical.\r\n\r\n**Error:**\r\n```\r\n[Vue warn]: Failed to resolve component: AppLogo\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n```\r\n\r\n[Search](https://github.com/s1kebeats/s1kebeats_client/blob/dev/components/modules/AppHeader/components/Search/Search.vue) component import in [AppHeader](https://github.com/s1kebeats/s1kebeats_client/blob/dev/components/modules/AppHeader/AppHeader.vue) doesn't work too.\r\n\r\n**Error:**\r\n```\r\n[Vue warn]: Failed to resolve component: Search\r\n[1] If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n```\r\n\r\nYou can visit `/register` route to see the import working in [form.vue](https://github.com/s1kebeats/s1kebeats_client/blob/dev/layouts/form.vue) and visit `/` route to see the import not working in [AppHeader](https://github.com/s1kebeats/s1kebeats_client/blob/dev/components/modules/AppHeader/AppHeader.vue).\r\n\r\n\r\n### Additional context\r\n\r\nI also have this in logs:\r\n\r\n`[Vue Router warn]: No match found for location with path \"/_nuxt/node_modules/.cache/vite/client/deps/\"`\r\n\r\n### Logs\r\n\r\n```shell-script\r\n[Vue Router warn]: No match found for location with path \"/_nuxt/node_modules/.cache/vite/client/deps/\"\r\n[Vue warn]: Failed to resolve component: AppLogo\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n[Vue warn]: Failed to resolve component: Search\r\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.\r\n```",[2983,2984],{"name":2884,"color":2885},{"name":2887,"color":2888},22857,"Valid imports fail in one specific component","2023-08-28T05:18:12Z","https://github.com/nuxt/nuxt/issues/22857",0.6896575,["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLog7igjq9RJt9aWyYs2CEv9jXe_2Mham9R-F4nDqPVM":-1},"/nuxt/ui/3249"]