\r\n | ^\r\n 4| \u003C/div>\r\n 5| \u003C/template>\r\n ❯ Proxy.clonedComponent.render node_modules/.pnpm/@nuxt+test-utils@3.14.0_@vue+test-utils@2.4.6_h3@1.12.0_happy-dom@14.12.3_nitropack@2.9.7_pla_3tccdhrwarphrx6od5vsqeppdq/node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:142:37\r\n ❯ renderComponentRoot node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6267:16\r\n ❯ ReactiveEffect.componentUpdateFn [as fn] node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4942:46\r\n ❯ ReactiveEffect.run node_modules/.pnpm/@vue+reactivity@3.4.37/node_modules/@vue/reactivity/dist/reactivity.cjs.js:181:19\r\n ❯ instance.update node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5073:16\r\n ❯ setupRenderEffect node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5083:5\r\n ❯ mountComponent node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4851:7\r\n ❯ processComponent node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4805:9\r\n ❯ patch node_modules/.pnpm/@vue+runtime-core@3.4.37/node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4334:11\r\n\r\nThis error originated in \"test.nuxt.test.ts\" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.\r\nThe latest test that might've caused the error is \"my test\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- If the error occurred after the test had been completed, this was the last documented test before it was thrown.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n Test Files 1 failed (1)\r\n Tests 1 failed (1)\r\n Errors 1 error\r\n Start at 18:00:20\r\n Duration 5.24s\n```\n",[2010,2013,2016],{"name":2011,"color":2012},"bug","d73a4a",{"name":2014,"color":2015},"good first issue","7057ff",{"name":2017,"color":2018},"vitest-environment","b60205",910,"Testing components that use CSS modules is failing","2024-12-19T21:35:48Z","https://github.com/nuxt/test-utils/issues/910",0.79677755,{"description":2025,"labels":2026,"number":2027,"owner":1985,"repository":1986,"state":2028,"title":2029,"updated_at":2030,"url":2031,"score":2032},"\r\n\r\n",[],1438,"closed","[Support] Workshops & Trainings link directs to HTTP 404","2023-12-04T11:28:56Z","https://github.com/nuxt/nuxt.com/issues/1438",0.740593,{"description":2034,"labels":2035,"number":2042,"owner":1985,"repository":2043,"state":2028,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### Description\n\nSorry if this information is available, but I could not find an answer in the docs or by searching.\n\nI was hoping to be able to let users select a theme that also included changing component defaults. \nUsing Vue/Vite (not Nuxt), is it possible to modify the full global configuration (`ui` object) at runtime (instead of having to pass props to or wrap each component)? \n\nI'm not 100% averse to a bit of monkey patching on my current project, but a supported solution would obviously be much much better.\n\nIf this is not currently possible, please consider this a suggestion, for example via an `ui` prop on the `App` component or a `useNuxtUi` composable.\n",[2036,2039],{"name":2037,"color":2038},"question","d876e3",{"name":2040,"color":2041},"v3","49DCB8",3290,"ui","Runtime configuration change?","2025-04-12T15:53:05Z","https://github.com/nuxt/ui/issues/3290",0.7503379,{"description":2049,"labels":2050,"number":2053,"owner":1985,"repository":2043,"state":2028,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.19.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: compatibilityDate, app, devtools, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.10, @nuxt/ui@3.0.0-alpha.10, @nuxt/eslint@0.7.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/great-orla-2l7wyw\n\n### Description\n\nThe checkbox-type items are no longer working as expected. When we copy and paste the code from the documentation [here](https://ui3.nuxt.dev/components/dropdown-menu#with-checkbox-items), the behavior is different from what is described.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2051,2052],{"name":2011,"color":2012},{"name":2040,"color":2041},3071,"[DropdownMenu] checkbox-type items are no longer working","2025-01-25T12:55:17Z","https://github.com/nuxt/ui/issues/3071",0.7629165,{"description":2059,"labels":2060,"number":2066,"owner":1985,"repository":1986,"state":2028,"title":2067,"updated_at":2068,"url":2069,"score":2070},"https://www.figma.com/design/KObqapBa7MXcOw78aPRL4E/%E2%9B%B0%EF%B8%8F---nuxt.com?node-id=775-13944&t=VQsmXmHirUicOKA7-0",[2061,2063],{"name":1996,"color":2062},"1ad6ff",{"name":2064,"color":2065},"design","00bd6f",1619,"[Enterprise] Support page rework","2024-07-26T17:57:33Z","https://github.com/nuxt/nuxt.com/issues/1619",0.7723698,{"description":2072,"labels":2073,"number":2076,"owner":1985,"repository":1986,"state":2028,"title":2077,"updated_at":2078,"url":2079,"score":2080},"Modules and Showcases are missing in mobile nav, presumably since migration from .md to Nuxt pages",[2074],{"name":2011,"color":2075},"ff281a",993,"[Code] Add missing links in mobile nav","2022-12-07T06:20:26Z","https://github.com/nuxt/nuxt.com/issues/993",0.78863204,{"description":2082,"labels":2083,"number":2001,"owner":1985,"repository":2087,"state":2028,"title":2088,"updated_at":2089,"url":2090,"score":2006},"### 📚 What are you trying to do?\r\n\r\nI need to implement OneTrustSDK and that thing needs a `data-domain-script` attribute on the `\u003Cscript>`-Tag. How can I get this data-attribute to render?\r\n\r\n### 🔍 What have you tried?\r\n\r\nI tried adding it in sciprts.global key:\r\n```typescript\r\n scripts: {\r\n globals: {\r\n oneTrust: {\r\n src: 'https://XXX.my.onetrust.eu/cdn/cookies/scripttemplates/otSDKStub.js',\r\n 'data-domain-script': 'XXXXXX-XXXXXXX-XXXXX',\r\n }\r\n },\r\n```\r\n\r\nI also tried adding it in my composable:\r\n```typescript\r\nexport function useScriptOneTrust\u003CT extends OneTrustApi>(options?: OneTrustInput) {\r\n return useRegistryScript\u003CT, typeof OneTrustOptions>('oneTrust', options => ({\r\n scriptInput: {\r\n 'src': 'https://XXX.my.onetrust.eu/cdn/cookies/scripttemplates/otSDKStub.js', // can't be bundled\r\n 'data-domain-script': options.domainScript,\r\n },\r\n }))\r\n}\r\n```\r\n\r\nThe only thing I can see being rendered is a preload link which fails because it needs a `\u003Cscript>`-Tag with a `data-domain-script` attribute:\r\n```\r\n\u003Clink rel=\"preload\" as=\"script\" href=\"https://XXX.my.onetrust.eu/cdn/cookies/scripttemplates/otSDKStub.js\" crossorigin=\"anonymous\" fetchpriority=\"low\" data-hid=\"1817094\">\r\n```\r\n\r\nI can see some data-cf-beacon attribute being set here, so I assumed it should be possible: https://github.com/nuxt/scripts/blob/main/src/runtime/registry/cloudflare-web-analytics.ts#L44\r\n\r\n_No response_",[2084],{"name":2085,"color":2086},"help wanted","008672","scripts","How can I add data-* attributes to the generated \u003Cscript> tag?","2024-09-17T11:34:02Z","https://github.com/nuxt/scripts/issues/268",{"description":2092,"labels":2093,"number":2099,"owner":1985,"repository":1985,"state":2028,"title":2100,"updated_at":2101,"url":2102,"score":2103},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚 -->\r\n\r\n### Is your feature request related to a problem? Please describe.\r\nLeaking of API keys and other sensitive information.\r\n\r\n\u003C!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\r\nIt's essential to keep secret information hidden from the client. The addition of privateRuntimeConfig is a good step forward, but the feature is somewhat incomplete, since it is [not trivial to know what code runs on client or server in nuxt](https://github.com/nuxt/nuxt.js/issues/2033), and it is [even noted in the guide](https://nuxtjs.org/docs/2.x/directory-structure/nuxt-config#privateruntimeconfig\r\n) that\r\n\r\n> Your private config could be exposed if you use $config outside of a server-only context (for example, if you use $config in fetch, asyncData or directly inside your template).\r\n\r\nRead: only using privateRuntimeConfig can't be relied upon - however that's what most people would expect from its name and most of the guide's description. Also, in actual development many people work on a code base and not many will look at stuff in a guide, especially if it comes with safe sounding names like this.\r\n\r\n### Describe the solution you'd like\r\nI would propose to add a function to check if the mentioned places (fetch, asyncData, template) contain the privateRuntimeConfig during dev/build/generate stages and display an error if it is detected.\r\n\r\nThat would bring developer peace of mind. Otherwise, if as devs we can't be sure that what we put into privateRuntimeConfig also stays private, it somewhat defeats its purpose.\r\n\r\n\r\n\u003C!-- A clear and concise description of what you want to happen. Adding some code examples would be neat! -->\r\n\r\n### Describe alternatives you've considered\r\nDifferent arch/labeling for nuxt that makes it clearer where functions run. \r\n\r\n### Additional context\r\nhttps://nuxtjs.org/docs/2.x/directory-structure/nuxt-config#privateruntimeconfig\r\n",[2094,2096],{"name":1996,"color":2095},"8DEF37",{"name":2097,"color":2098},"2.x","d4c5f9",9087,"[security] Check for privateRuntimeConfig Leaks","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9087",0.78924024,["Reactive",2105],{},["Set"],["ShallowReactive",2108],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"LTnJG291Qj-yALIDvujBuntCg9se1ldnChQZ5wo76FU":-1},"/nuxt/nuxt.com/1341"]