\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nconst dynamic_image_name = 'zero-config.svg';\r\n\u003C/script>\r\n```\r\n\r\nthen this is rendered as \r\n```html\r\n\u003Cimg src=\"~/assets/zero-config.svg\" alt=\"Discover Nuxt 3\">\r\n```\r\nwithout correctly resolving (and copying) the image, thus it doesn't show in the browser.\n\n### Additional context\n\nRefs https://github.com/nuxt/framework/pull/6635.\n\n### Logs\n\n_No response_",[3158,3161],{"name":3159,"color":3160},"documentation","5319e7",{"name":3162,"color":3163},"dx","C39D69",14766,"nuxt","open","Assets with dynamic names are not resolved","2025-01-11T09:07:17Z","https://github.com/nuxt/nuxt/issues/14766",0.73311263,{"description":3172,"labels":3173,"number":3174,"owner":3165,"repository":3175,"state":3176,"title":3177,"updated_at":3178,"url":3179,"score":3180},"On [https://dev.nuxt.com/docs/3.x](https://dev.nuxt.com/docs/3.x) in dark mode, the \"Modular and instinctive architecture\" section has an assets misnaming bug :\n\n**Layouts-dark.svg** should be **layouts-dark.svg**\n**App-dark.svg** should be **app-dark.svg**\n\nThis only happens on the staging env.\n\n",[],744,"nuxt.com","closed","[Docs] Assets misnaming on `3.x`","2023-02-15T12:30:54Z","https://github.com/nuxt/nuxt.com/issues/744",0.46962374,{"description":3182,"labels":3183,"number":3187,"owner":3165,"repository":3165,"state":3176,"title":3188,"updated_at":3189,"url":3190,"score":3191},"I think you need something in the documentation to reflect the fact that ~/assets points to /app/assets here\n\nhttps://nuxt.com/docs/4.x/getting-started/assets\n\nand the v4 UI docs needs to say to add css: ['~/assets/css/main.css'], to nuxt.config.ts\n\nhttps://nuxt.com/modules/ui\n\nProbably need to mention the new /app structure here as well\n\nhttps://nuxt.com/docs/4.x/getting-started/routing",[3184],{"name":3185,"color":3186},"pending triage","E99695",32808,"Update v4 Documentation /app/assets UI","2025-09-03T20:14:24Z","https://github.com/nuxt/nuxt/issues/32808",0.7111525,{"labels":3193,"number":3198,"owner":3165,"repository":3165,"state":3176,"title":3199,"updated_at":3200,"url":3201,"score":3202},[3194,3195],{"name":3185,"color":3186},{"name":3196,"color":3197},"2.x","d4c5f9",7665,"since nuxt@2.13.3 some modern files are missing?","2023-01-22T15:36:01Z","https://github.com/nuxt/nuxt/issues/7665",0.72168905,{"description":3204,"labels":3205,"number":3207,"owner":3165,"repository":3165,"state":3176,"title":3208,"updated_at":3209,"url":3210,"score":3211},"I have a big project here that I tried to update for `nuxt` to `nuxt-edge`.\r\n\r\nWhen I run `nuxt build` I see a lot of errors like this:\r\n```\r\nConflict: Multiple assets emit to the same filename xxxx.css\r\n```",[3206],{"name":3196,"color":3197},3152,"Conflict: Multiple assets emit to the same filename","2023-01-18T16:10:06Z","https://github.com/nuxt/nuxt/issues/3152",0.7278976,{"description":3213,"labels":3214,"number":3218,"owner":3165,"repository":3175,"state":3176,"title":3219,"updated_at":3220,"url":3221,"score":3222},"\n",[3215],{"name":3216,"color":3217},"bug","ff281a",567,"[Docs] Framework v3 asset error on load","2023-02-15T12:30:49Z","https://github.com/nuxt/nuxt.com/issues/567",0.7300366,{"description":3224,"labels":3225,"number":3218,"owner":3165,"repository":3229,"state":3176,"title":3230,"updated_at":3231,"url":3232,"score":3222},"Hello, I'm having a hard time understanding and finding information on how to mock useFetch/useAsyncData returned data. \r\nI've tried using the following as well as an MSW server included in `vitest.setup.ts` but with no success:\r\n\r\nHere's an example component `pages/test.vue`:\r\n```\r\n\u003Cscript setup>\r\nconst { data: users } = useFetch('https://jsonplaceholder.typicode.com/users');\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cul>\r\n \u003Cli v-for=\"user in users\" :key=\"user.id\">\r\n \u003Cp>{{ user.id }}\u003C/p>\r\n \u003Cp>{{ user.name }}\u003C/p>\r\n \u003C/li>\r\n \u003C/ul>\r\n\u003C/template>\r\n```\r\n`pages/__tests__/Test.spec.ts`:\r\n```\r\n// @vitest-environment nuxt\r\nimport { describe, expect, it } from 'vitest';\r\nimport { mount } from '@vue/test-utils';\r\nimport { mockNuxtImport } from 'nuxt-vitest/utils';\r\nimport Test from '../test.vue';\r\n\r\nmockNuxtImport('useFetch', () => {\r\n return () =>\r\n vi.fn(() => {\r\n return {\r\n error: undefined,\r\n data: [\r\n {\r\n id: 1,\r\n name: 'John Doe',\r\n },\r\n ],\r\n pending: false,\r\n refresh: vi.fn(),\r\n };\r\n });\r\n});\r\n\r\nvi.stubGlobal('useFetch', () => {\r\n return () =>\r\n vi.fn(() => {\r\n return {\r\n error: undefined,\r\n data: [\r\n {\r\n id: 1,\r\n name: 'John Doe',\r\n },\r\n ],\r\n pending: false,\r\n refresh: vi.fn(),\r\n };\r\n });\r\n});\r\n\r\ndescribe('Test', () => {\r\n const wrapper = mount(Test);\r\n\r\n it('should render correctly', () => {\r\n expect(wrapper.html()).toMatchSnapshot();\r\n });\r\n});\r\n```\r\nIn the snapshot I can see that no data was fetched and nothing changes no matter which above mentioned method I try to mock the data with.\r\n`pages/__tests__/__snapshots__/Test.spec.ts.snap`\r\n```\r\n// Vitest Snapshot v1, https://vitest.dev/guide/snapshot.html\r\n\r\nexports[`Test > should render correctly 1`] = `\"\u003Cul>\u003C/ul>\"`;\r\n```\r\n`vitest.config.ts`\r\n```\r\nimport { defineVitestConfig } from 'nuxt-vitest/config';\r\n\r\nexport default defineVitestConfig({\r\n test: {\r\n environment: 'happy-dom',\r\n setupFiles: ['./vitest.setup.ts'],\r\n },\r\n});\r\n```\r\n`vitest.setup.ts`\r\n```\r\nimport { rest } from 'msw';\r\nimport { setupServer } from 'msw/node';\r\n\r\nconst users = [\r\n {\r\n id: 1,\r\n name: 'John Doe',\r\n },\r\n];\r\n\r\nexport const restHandlers = [\r\n rest.get('https://jsonplaceholder.typicode.com/users', (req, res, ctx) => {\r\n return res(ctx.status(200), ctx.json(users));\r\n }),\r\n];\r\n\r\nconst server = setupServer(...restHandlers);\r\n\r\n// Start server before all tests\r\nbeforeAll(() => server.listen({ onUnhandledRequest: 'error' }));\r\n\r\n// Close server after all tests\r\nafterAll(() => server.close());\r\n\r\n// Reset handlers after each test `important for test isolation`\r\nafterEach(() => server.resetHandlers());\r\n```",[3226],{"name":3227,"color":3228},"vitest-environment","b60205","test-utils","API data mocking","2023-12-02T00:32:12Z","https://github.com/nuxt/test-utils/issues/567",{"description":3234,"labels":3235,"number":3240,"owner":3165,"repository":3165,"state":3176,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v21.0.0\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@10.2.0\r\n- Builder: -\r\n- User Config: devtools, router, alias, image, modules, imports, routeRules, nitro, experimental, app\r\n- Runtime Modules: @vueuse/nuxt@10.4.1, @nuxt/image-edge@1.0.0-rc.3-28271297.f1bc89f, @formkit/auto-animate/nuxt@0.8.0, @nuxtjs/robots@3.0.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n\r\n\r\n***Unfortunately, the error is not a constant one, as it happens to occur on some occassions***\r\n\r\n### Describe the bug\r\n\r\n\r\n\r\n# PostCSS mistakens script tag for style tag once in a while.\r\nThis error happens sometimes when I make little changes and this one happened when I added a new function to Vue script[setup] tag. I don't get any results after reloading my current page, or reverting my changes, but only until I restart my development server, and most times by deleting the **.nuxt** folder. I initially thought that this error was due to my ***experimental*** option set with at least one key in ***nuxt.config.ts***, but it still occurred without any ***experimental*** set.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3236,3239],{"name":3237,"color":3238},"3.x","29bc7f",{"name":3185,"color":3186},23957,"Error on keywords that shouldn't be unknown","2023-10-26T16:06:38Z","https://github.com/nuxt/nuxt/issues/23957",0.73327136,{"description":3246,"labels":3247,"number":3256,"owner":3165,"repository":3165,"state":3176,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.10.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.6.1\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-lbutem?file=pages%2Findex.vue\n\n### Describe the bug\n\nLinks to files in Nuxt's `public` folder are sometimes broken if the path starts with `/assets/`, as it will be replaced with `/&/assets/`. It works fine on the initial render of an `img` element, but if a re-render updates that element, this issue occurs.\n\nReproduction steps:\n1. Open the minimal reproduction link.\n2. Click the link to page 2.\n3. Notice the image is now broken because its `href` was jumbled.\n\n### Additional context\n\nI have only tested this for images (`\u003Cimg src=\"/assets/...\" />`). I don't know if it applies to other forms of references to static assets in the `public/assets` folder.",[3248,3250,3253],{"name":3216,"color":3249},"d73a4a",{"name":3251,"color":3252},"vite","3574D1",{"name":3254,"color":3255},"upstream","E8A36D",30107,"Can't name folder \"assets\" in `public` without issues re-rendering components","2024-12-02T10:04:42Z","https://github.com/nuxt/nuxt/issues/30107",0.735439,{"labels":3262,"number":3265,"owner":3165,"repository":3165,"state":3176,"title":3266,"updated_at":3267,"url":3268,"score":3269},[3263,3264],{"name":3185,"color":3186},{"name":3196,"color":3197},8274,"Invalid CSS asset filenames generated, breaks site operation","2023-01-22T15:38:17Z","https://github.com/nuxt/nuxt/issues/8274",0.7372839,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f4XA-IhTDE3GE1eA24EtEBfnBw5f0lIQJSJGui3Rsd7g":-1},"/nuxt/test-utils/744"]