",[],1885,"nuxt.com","[Nuxt Website]: \u003Cno response> Failed to fetch","2025-05-03T08:24:49Z","https://github.com/nuxt/nuxt.com/issues/1885",0.76346743,{"description":2882,"labels":2891,"number":2892,"owner":2875,"repository":2875,"state":2876,"title":2886,"updated_at":2893,"url":2894,"score":2889},[],31986,"2025-05-03T06:58:04Z","https://github.com/nuxt/nuxt/issues/31986",{"description":2896,"labels":2897,"number":2901,"owner":2875,"repository":2875,"state":2876,"title":2902,"updated_at":2903,"url":2904,"score":2905},"## Motivation\r\n\r\nNuxt leverage the unjs ecosystem for core parts of the framework, mainly Nitro, H3 and oftech.\r\nWhile the UnJS ecosystem can be used stand-alone, the majority of its users comes from Nuxt.\r\n\r\nYet, the experience while looking for information about Nuxt in general is often disjointed, due to Nuxt.com and Nitro being separated website, and h3/ofetch currently not having dedicated websites https://github.com/unjs/h3/issues/418\r\n\r\nThis makes it hard to reason about Nuxt for newcomers, when they will look for how to do something in the docs, won't find it, then have to navigate to the Nitro website, or the github READMEs for H3 or oftech, or googling / finding information in articles.\r\n\r\nWith separated websites, the information is not searchable and accessible easily. We could have a single algolia index that search throughout Nuxt/Nitro/H3. \r\nIt's something that cloudflare does well, the search bar can jump from one product to the other seamlessly.\r\n\r\n\u003Cimg width=\"1007\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/582fe321-1a2e-4e12-9729-1cfd65aa73d8\">\r\n\r\n## Proposal\r\n\r\n### For Nuxt\r\n\r\nIntegrate H3, Nitro and ofetch in the nuxt.com website, such so that we have \r\n\r\n- https://nuxt.com/docs/nitro/\r\n- https://nuxt.com/docs/h3/\r\n- https://nuxt.com/docs/$fetch/\r\n\r\nand one search bar that can be used to reference the content of all 3.\r\nThis would remove the duplicated content accross Nuxt and these website, are they would use the *same* source.\r\n\r\n### For Nitro, H3 and ofetch\r\n\r\nSince these tools are meant to be used either standalone or with Nuxt, we could have a nuxt version for them. \r\nThis can be implemented with a NuxtOnly and a StandAlone component that we can use to wrap docs paragraph or code examples.\r\n\r\nUsing Nitro as an example, this would serve multiple purposes : \r\n\r\n- Documentation for Nitro and Nuxt would share the same source of truth\r\n- Nitro would still have a standalone website that would be identical to what it is today\r\n- Nitro would feel more integrated under the Nuxt umbrella as its docs would be accessible without navigating to an external page. Wether they're the same Nuxt app, or there's is one website for each subdocs is an implementation detail.\r\n\r\nAdditionally, the Nitro website could use a toggle like the vue composition/options api switcher : \r\n \u003Cimg width=\"304\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/d8164560-1e84-42e2-936e-a91cdf5e38c7\">\r\nThis toggle would enable nuxt or standalone instructions. It would be hidden inhttps://nuxt.com/docs/nitro/ which would default to Nuxt, and would be either hidden or visible in https://nitro.unjs.io/ which would default to standalone.\r\n\r\n## Extra toughts\r\n\r\nThere are also additional libraries that are used by Nuxt such as vue, vite, vue-router, but this doesn't affect the experience as bad as Nitro/h3. However a similar system can be adopted for unjs libraries that are end-user facing and auto-imported.\r\nWhere this makes sense. Perhaps Unstorage/db0 as they come with Nitro/Nuxt.\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).",[2898],{"name":2899,"color":2900},"documentation","5319e7",21930,"[Proposal] Unified Nuxt Documentation Experience","2024-06-30T11:08:20Z","https://github.com/nuxt/nuxt/issues/21930",0.76409423,{"description":2907,"labels":2908,"number":2911,"owner":2875,"repository":2875,"state":2876,"title":2912,"updated_at":2913,"url":2914,"score":2915},"Nuxt has full support for payload extraction in production, when run with `nuxi generate` or `nuxi build --prerender` but there's no way to experience this in development (or identify possible bugs).\n\nIt would be good to support payload extraction when explicitly enabled by setting `nitro.static` to `true` (or by enabling `experimental.payloadExtraction` directly).\n\nWe might also consider moving `payloadExtraction` out of experimental namespace and/or renaming it.",[2909,2910],{"name":2866,"color":2867},{"name":2869,"color":2870},30679,"payload extraction support in development mode","2025-01-21T09:09:47Z","https://github.com/nuxt/nuxt/issues/30679",0.7704446,{"description":2917,"labels":2918,"number":2921,"owner":2875,"repository":2875,"state":2876,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Describe the feature\n\nHey I am currently moving a big project from standard vue3 to nuxt, and have to rewrite most of my options api code to composition api..\r\n\r\nThe issue mostly is that some features are not there in composition api and when one is missing i can't \"link\" it to options api and then i got to go down the rabbit hole of changing my code to use composition api although it's already completely valid options api code.\r\n\r\nFor real, props, it is an awesome framework and it's very impressive etc.\r\n\r\nBUT.... in my opinion, it is kind of weird that it does not fully support vue (from my pov) as i do have to use so much \"special\" vue code instead of easily porting my app.\r\n\r\nI am still continuing to use nuxt for now but if you were able to make the transition a bit easier, i think a lot of people would use nuxt instead of plain old vue 3.\r\n\r\nI am willing to help with the adoption by saying what needs to happen (for a project like mine) to be easily portable to nuxt, if that is helpful.\r\n\r\nLmk what u think :) \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).",[2919,2920],{"name":2866,"color":2867},{"name":2869,"color":2870},21670,"Missing Support (Or documentation of) Options API with Nuxt","2024-06-30T11:08:29Z","https://github.com/nuxt/nuxt/issues/21670",0.7717074,{"description":2927,"labels":2928,"number":2932,"owner":2875,"repository":2885,"state":2933,"title":2934,"updated_at":2935,"url":2936,"score":2937},"The goal here is to migrate all of our websites around `nuxt.com` without the multi-source. All the documentations stays on `*.nuxt.com` subdomains.\n\n## Nuxt.com\n\n- [x] Landing page nuxtlabs/nuxt.com#405\n- [x] Framework v3\n - [x] Landing page nuxtlabs/nuxt.com#406\n - [x] Links to `v3.nuxtjs.org` (`v3.nuxt.com`) nuxtlabs/nuxt.com#539\n- [x] Framework v2\n - [x] Landing page\n - [x] Links to `nuxtjs.org` (`v2.nuxt.com`) nuxtlabs/nuxt.com#539\n- [x] Integrations\n - [x] Landing page (list of modules)\n - [x] Links as filters (`officials`/`community`/`3rd party`) nuxtlabs/nuxt.com#538\n- [x] Projects page nuxtlabs/nuxt.com#403\n- [x] Resources\n - [x] Blog\n - [x] Case Studies\n - [x] Design Kit\n - [x] Live Events\n - [x] Showcases\n- [x] Community\n - [x] About nuxtlabs/nuxt.com#541\n - [x] Guide nuxtlabs/nuxt.com#542\n - [x] Repositories nuxtlabs/nuxt.com#525\n - [x] Nuxters nuxtlabs/nuxt.com#543\n - [x] Partners nuxtlabs/nuxt.com#526\n- [x] Company\n - [x] About\n - [x] Careers\n - [x] Partners nuxtlabs/nuxt.com#540\n - [x] Support\n - [x] Contact\n\n## `v3.nuxt.com` nuxtlabs/nuxt.com#535\n\n## `v2.nuxt.com` nuxtlabs/nuxt.com#534\n\n## `content.nuxt.com` nuxtlabs/nuxt.com#536\n\n## `image.nuxt.com` nuxtlabs/nuxt.com#537\n\n\n",[2929],{"name":2930,"color":2931},"roadmap","ff7a1a",533,"closed","MVP","2022-11-17T11:44:04Z","https://github.com/nuxt/nuxt.com/issues/533",0.74531895,{"description":2939,"labels":2940,"number":2932,"owner":2875,"repository":2950,"state":2933,"title":2951,"updated_at":2952,"url":2953,"score":2937},"This happens on any test when I trigger a click. Not yet tying any other trigger events.\r\n\r\nError\r\n`TypeError: Cannot read properties of undefined (reading 'error')`\r\n\r\nVersion\r\n`\"nuxt-vitest\": \"0.10.5\",`\r\n\r\nConfig\r\n```\r\nimport { defineVitestConfig } from 'nuxt-vitest/config';\r\n\r\nexport default defineVitestConfig({\r\n test: {\r\n environment: 'nuxt',\r\n },\r\n});\r\n```\r\n\r\nTest\r\n```\r\nimport { describe, it, expect } from 'vitest';\r\nimport { mount, VueWrapper } from '@vue/test-utils';\r\n\r\nimport ApiTypeTabsDescription from '../components/ApiTypeTabsDescription.vue';\r\nlet wrapper: VueWrapper;\r\nwrapper = mount(ApiTypeTabsDescription);\r\n\r\ndescribe('ApiTypeTabsDescription', () => {\r\n it('More text is visible', async () => {\r\n const toggle = wrapper.find('.register-show-more-btn-text');\r\n await toggle.trigger('click');\r\n await wrapper.vm.$nextTick();\r\n expect(wrapper.find('.register-show-more-description').exists()).toBe(true);\r\n });\r\n});\r\n```\r\n\r\n```\r\nTypeError: Cannot read properties of undefined (reading 'error')\r\n ❯ HTMLScriptElement.dispatchEvent node_modules/.pnpm/happy-dom@12.1.2/node_modules/happy-dom/src/event/EventTarget.ts:102:54\r\n ❯ HTMLScriptElement.dispatchEvent node_modules/.pnpm/happy-dom@12.1.2/node_modules/happy-dom/src/nodes/element/Element.ts:920:29\r\n ❯ Function.dispatchError node_modules/.pnpm/happy-dom@12.1.2/node_modules/happy-dom/src/window/WindowErrorUtility.ts:60:32\r\n ❯ Function.loadExternalScript node_modules/.pnpm/happy-dom@12.1.2/node_modules/happy-dom/src/nodes/html-script-element/HTMLScriptElementUtility.ts:54:24\r\n```",[2941,2944,2947],{"name":2942,"color":2943},"vitest-environment","b60205",{"name":2945,"color":2946},"needs reproduction","DE7793",{"name":2948,"color":2949},"closed-by-bot","ededed","test-utils","When using trigger('click') get this error & tests don't run TypeError: Cannot read properties of undefined (reading 'error')","2023-12-13T01:51:03Z","https://github.com/nuxt/test-utils/issues/533",{"description":2955,"labels":2956,"number":2957,"owner":2875,"repository":2950,"state":2933,"title":2958,"updated_at":2959,"url":2960,"score":2961},"Right now the docs has a quite limitation and there is no guidance on integrating with a full Nuxt app which contains pages with may api calls, not just plugin or components let alone ts module import.\r\n\r\nIt would be much appreciated if you can expand the docs on for a more specific cases or may be some examples on this repo or say a fiddle, codepen, codesandbox ?",[],265,"more docs on how to mock test for a page","2023-12-02T00:18:11Z","https://github.com/nuxt/test-utils/issues/265",0.75142896,{"description":2955,"labels":2963,"number":2964,"owner":2875,"repository":2950,"state":2933,"title":2958,"updated_at":2965,"url":2966,"score":2961},[],355,"2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/355",["Reactive",2968],{},["Set"],["ShallowReactive",2971],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fd1Z38mcPi00sOT0d5zh4iSxqa__KZBKnziIpahD80ck":-1},"/nuxt/nuxt.com/1398"]