\n \u003C/NuxtLink>\n \u003CNuxtLink v-slot=\"{ isActive }\" to=\"/movie\" :title=\"$t('Movies')\" data-testid=\"movies-link\">\n \u003Cdiv\n text-2xl\n :class=\"isActive ? 'i-ph-film-strip-fill text-primary' : 'i-ph-film-strip'\"\n />\n \u003C/NuxtLink>\n \u003CNuxtLink v-slot=\"{ isActive }\" to=\"/tv\" :title=\"$t('TV Shows')\" data-testid=\"tv-shows-link\">\n \u003Cdiv\n text-2xl\n :class=\"isActive ? 'i-ph-television-simple-fill text-primary' : 'i-ph-television-simple'\"\n />\n \u003C/NuxtLink>\n \u003CNuxtLink v-slot=\"{ isActive }\" to=\"/search\" :title=\"$t('Search')\" data-testid=\"search-link\">\n \u003Cdiv\n text-2xl\n :class=\"isActive ? 'i-ph-magnifying-glass-fill text-primary' : 'i-ph-magnifying-glass'\"\n />\n \u003C/NuxtLink>\n \u003C/div>\n\u003C/template>\n```\n\n`NavBar.nuxt.test.ts File`\n```\nimport type { VueWrapper } from '@vue/test-utils'\nimport { mountSuspended } from '@nuxt/test-utils/runtime'\nimport { describe, expect, it } from 'vitest'\n\nimport NavBar from './NavBar.vue'\n\ndescribe('navBar', () => {\n it('renders Home link correctly', async () => {\n const wrapper = await mountSuspended(NavBar)\n\n // test true to be true\n expect(true).toBe(true)\n })\n```\n\n### Describe the bug\n\nIm trying to to a simple component test and I think it's failing to mock NuxtLink with slots when it is destruturing the property isActive\n\n### Additional context\n\n_No response_\n\n### Logs\n\nhttps://github.com/Archetipo95/movies/actions/runs/12358331784/job/34488575188?pr=2",[1984],{"name":1985,"color":1986},"pending triage","5D08F5",1042,"nuxt","test-utils","open","TypeError: Cannot destructure property 'isActive' of 'undefined' as it is undefined - NuxtLink","2024-12-16T17:53:11Z","https://github.com/nuxt/test-utils/issues/1042",0.7528411,{"description":1996,"labels":1997,"number":2001,"owner":1988,"repository":1989,"state":1990,"title":2002,"updated_at":2003,"url":2004,"score":2005},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.8.1`\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.19`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-gee6qy?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOnce I expose a variable called `error` within the setup, the component fails to render. \r\nSince everything works within the dev server / build, I suspect this is something within `@nuxt/test-utils`\r\n\r\nAfter renaming the `error` variable to something else, the component can be mounted within the tests again.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ clonedComponent.render node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:128:44\r\n 126| renderContext[key] = passedProps[key];\r\n 127| }\r\n 128| return render.call(this, renderContext, ...args);\r\n | ^\r\n 129| } : void 0,\r\n 130| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:868:16\r\n ❯ ReactiveEffect.componentUpdateFn node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:46\r\n ❯ ReactiveEffect.run node_modules/@vue/reactivity/dist/reactivity.cjs.js:174:19\r\n ❯ instance.update node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6053:16\r\n ❯ setupRenderEffect node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6063:5\r\n ❯ eval node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1613:9\r\n\r\nThis error originated in \"test/app.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 \"Should mount\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- This was the last recorded test before the error was thrown, if error originated after test finished its execution.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n```\r\n```\r\n",[1998],{"name":1999,"color":2000},"bug","d73a4a",684,"mountSuspended fails: 'set' on proxy: trap returned falsish for property 'error'","2025-03-14T15:14:45Z","https://github.com/nuxt/test-utils/issues/684",0.7586668,{"description":2007,"labels":2008,"number":2016,"owner":1988,"repository":2017,"state":1990,"title":2018,"updated_at":2019,"url":2020,"score":2021},"### Reproduction\n\n````\n\u003Ctemplate>\n \u003CUChip text=\"test\" size=\"3xl\">\n \u003CUButton icon=\"i-lucide-mail\" color=\"neutral\" variant=\"subtle\" />\n \u003C/UChip>\n\u003C/template>\n````\n\n### Description\n\nHey,\n\nThanks for your great work.\n\nI have noticed this on a few elements in UI3, but especaily here padding just is not right. Yes of course you can change it, but i belive there needs to be some sane defaults across all elements.\n\nText in chip, and even a simple number is almost unreadable see screenshot below. Happy to open a pr or list all other elements where this seems to have happened (one that comes to mind is UAvatar https://github.com/nuxt/ui/issues/3558).\n\n\n\n### Additional context\n\nThis example is directly from the UI website",[2009,2010,2013],{"name":1999,"color":2000},{"name":2011,"color":2012},"v3","49DCB8",{"name":2014,"color":2015},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.7685553,{"description":2023,"labels":2024,"number":2026,"owner":1988,"repository":1989,"state":2027,"title":2028,"updated_at":2029,"url":2030,"score":2031},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v18.19.0\n- Nuxt Version: 3.12.4\n- CLI Version: 3.13.2\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/inouetakuya/nuxt-test-utils-playground/pull/3\n\nGitHub: https://github.com/inouetakuya/nuxt-test-utils-playground/pull/3\n\n### Describe the bug\n\nHere is the page component using the Options API.\n\n```vue\n\u003Cscript lang=\"ts\"> \nexport default defineNuxtComponent({ \n name: 'OptionsApiPage', \n setup() { \n return { \n greetingInSetup: 'Hello, setup!', \n }; \n }, \n async asyncData() { \n return { \n greetingInAsyncData: 'Hello, asyncData!', \n }; \n }, \n data() { \n return { \n greetingInData: 'Hello, data!', \n }; \n }, \n computed: { \n greetingInComputed() { \n return 'Hello, computed property!'; \n }, \n }, \n}); \n\u003C/script> \n \n\u003Ctemplate> \n \u003Cp data-testid=\"greeting-in-setup\">greetingInSetup: {{ greetingInSetup }}\u003C/p> \n \u003Cp data-testid=\"greeting-in-async-data\"> \n greetingInAsyncData: {{ greetingInAsyncData }} \n \u003C/p> \n \u003Cp data-testid=\"greeting-in-data\">greetingInData: {{ greetingInData }}\u003C/p> \n \u003Cp data-testid=\"greeting-in-computed\"> \n greetingInComputed: {{ greetingInComputed }} \n \u003C/p> \n\u003C/template>\n```\n\nWhen testing this page component using the mountSuspended method, the data and computed properties of the Options API are not rendered. \n\nOn the other hand, if the same page component is tested with the mount method, both the Options API data and the computed properties are rendered.\n\n```ts\nimport { mountSuspended } from '@nuxt/test-utils/runtime'; \nimport { mount, flushPromises } from '@vue/test-utils'; \nimport OptionsApiPage from '~/pages/options-api.vue'; \n \ndescribe('OptionsApiPage', () => { \n let wrapper; \n \n describe('Using mountSuspended', () => { \n beforeEach(async () => { \n wrapper = await mountSuspended(OptionsApiPage, { \n route: '/options-api', \n }); \n }); \n \n it('should render greeting in setup', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-setup\"]').text()).toBe( \n 'greetingInSetup: Hello, setup!', \n ); \n }); \n \n it('should render greeting in asyncData', () => { \n expect( \n wrapper.find('[data-testid=\"greeting-in-async-data\"]').text(), \n ).toBe('greetingInAsyncData: Hello, asyncData!'); \n }); \n \n it('should render greeting in data', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-data\"]').text()).toBe( \n 'greetingInData: Hello, data!', \n ); \n }); \n \n it('should render greeting in computed', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-computed\"]').text()).toBe( \n 'greetingInComputed: Hello, computed property!', \n ); \n }); \n }); \n \n describe('Using mount', () => { \n beforeEach(async () => { \n const component = defineComponent({ \n components: { OptionsApiPage }, \n template: '\u003CSuspense>\u003COptionsApiPage />\u003C/Suspense>', \n }); \n wrapper = mount(component); \n await flushPromises(); \n }); \n \n it('should render greeting in setup', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-setup\"]').text()).toBe( \n 'greetingInSetup: Hello, setup!', \n ); \n }); \n \n it('should render greeting in asyncData', () => { \n expect( \n wrapper.find('[data-testid=\"greeting-in-async-data\"]').text(), \n ).toBe('greetingInAsyncData: Hello, asyncData!'); \n }); \n \n it('should render greeting in data', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-data\"]').text()).toBe( \n 'greetingInData: Hello, data!', \n ); \n }); \n \n it('should render greeting in computed', () => { \n expect(wrapper.find('[data-testid=\"greeting-in-computed\"]').text()).toBe( \n 'greetingInComputed: Hello, computed property!', \n ); \n }); \n }); \n});\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n$ npm test\n\n> test\n> vitest run\n\n\n RUN v2.0.5 /Users/inouetakuya/src/github.com/inouetakuya/nuxt-test-utils-playground\n\nstdout | pages/script-setup.nuxt.spec.ts\n\u003CSuspense> is an experimental feature and its API will likely change.\n\nstdout | pages/options-api.nuxt.spec.ts\n\u003CSuspense> is an experimental feature and its API will likely change.\n\n ❯ pages/options-api.nuxt.spec.ts (8)\n ❯ OptionsApiPage (8)\n ❯ Using mountSuspended (4)\n ✓ should render greeting in setup\n ✓ should render greeting in asyncData\n × should render greeting in data\n × should render greeting in computed\n ✓ Using mount (4)\n ✓ pages/script-setup.nuxt.spec.ts (1)\n ✓ utils/example-util.spec.ts (1)\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\n\n FAIL pages/options-api.nuxt.spec.ts > OptionsApiPage > Using mountSuspended > should render greeting in data\nAssertionError: expected 'greetingInData:' to be 'greetingInData: Hello, data!' // Object.is equality\n\nExpected: \"greetingInData: Hello, data!\"\nReceived: \"greetingInData:\"\n\n ❯ pages/options-api.nuxt.spec.ts:28:71\n 26|\n 27| it('should render greeting in data', () => {\n 28| expect(wrapper.find('[data-testid=\"greeting-in-data\"]').text()).toBe(\n | ^\n 29| 'greetingInData: Hello, data!',\n 30| );\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯\n\n FAIL pages/options-api.nuxt.spec.ts > OptionsApiPage > Using mountSuspended > should render greeting in computed\nAssertionError: expected 'greetingInComputed:' to be 'greetingInComputed: Hello, computed p…' // Object.is equality\n\nExpected: \"greetingInComputed: Hello, computed property!\"\nReceived: \"greetingInComputed:\"\n\n ❯ pages/options-api.nuxt.spec.ts:34:75\n 32|\n 33| it('should render greeting in computed', () => {\n 34| expect(wrapper.find('[data-testid=\"greeting-in-computed\"]').text()).toBe(\n | ^\n 35| 'greetingInComputed: Hello, computed property!',\n 36| );\n\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯\n\n Test Files 1 failed | 2 passed (3)\n Tests 2 failed | 8 passed (10)\n Start at 16:38:07\n Duration 740ms (transform 303ms, setup 513ms, collect 188ms, tests 41ms, environment 237ms, prepare 331ms)\n```\n",[2025],{"name":1985,"color":1986},961,"closed","mountSuspended does not render Options API's data and computed properties","2024-10-08T13:30:47Z","https://github.com/nuxt/test-utils/issues/961",0.69248134,{"description":2033,"labels":2034,"number":2035,"owner":1988,"repository":2036,"state":2027,"title":2037,"updated_at":2038,"url":2039,"score":2040},"Hello,\nadding your package to the a repository for deploying breaks the Rollup build step.\n\n## Minimal reproducible example\n```\nnode --version\nv20.17.0\npnpm --version\n9.11.0\n```\n- `pnpm create cloudflare@latest my-nuxt-app --framework=nuxt`\n- `cd my-nuxt-app`\n- `pnpx nuxi module add icon` (taken from your doc)\n- `pnpm build`\nI get the following error:\n\n```\n[nitro 23:41:30] ERROR RollupError: .nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js (1:9): \"stdin\" is not exported by \"node_modules/.pnpm/unenv@1.10.0/node_modules/unenv/runtime/node/process/index.mjs\", imported by \".nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js\".\n\n\n1: import { stdin, stdout } from \"node:process\";\n ^\n2: import f from \"node:readline\";\n3: import { WriteStream } from \"node:tty\";\n\n\n[23:41:30] ERROR .nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js (1:9): \"stdin\" is not exported by \"node_modules/.pnpm/unenv@1.10.0/node_modules/unenv/runtime/node/process/index.mjs\", imported by \".nuxt/dist/server/_nuxt/prompt-DuW0Lom1.js\".\n```\n\nThanks.",[],274,"icon","Rollup issue - Adding the package breaks the build step","2024-10-28T13:36:54Z","https://github.com/nuxt/icon/issues/274",0.6948113,{"description":2042,"labels":2043,"number":2047,"owner":1988,"repository":2017,"state":2027,"title":2048,"updated_at":2049,"url":2050,"score":2051},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, components, css, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0, @pinia/nuxt@0.10.1, compodium@0.1.0-beta.5\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUInputMenu :items=\"idList\" v-model=\"value\" />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(0)\nconst idList = ref([168, 170, 203])\n\u003C/script>\n```\n\n### Description\n\nIf adding array of numbers to InputMenu the menu isn't closing after choosing a number.\nOnly way to close it is double-clicking on the dropdown arrow.\nThe Console shows an error in useFilter.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: string.normalize is not a function\n at contains (useFilter.js?v=87101672:23:21)\n at InputMenu.vue:114:18\n at wrappedFn (reactivity.esm-bundler.js?v=87101672:820:19)\n at Array.filter (\u003Canonymous>)\n at apply (reactivity.esm-bundler.js?v=87101672:828:27)\n at Proxy.filter (reactivity.esm-bundler.js?v=87101672:720:12)\n at InputMenu.vue:112:50\n at Array.map (\u003Canonymous>)\n at ComputedRefImpl.fn (InputMenu.vue:112:27)\n at refreshComputed (reactivity.esm-bundler.js?v=87101672:353:29)\n```",[2044,2045,2046],{"name":1999,"color":2000},{"name":2011,"color":2012},{"name":2014,"color":2015},3606,"Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.7078825,{"description":2053,"labels":2054,"number":2055,"owner":1988,"repository":2036,"state":2027,"title":2056,"updated_at":2057,"url":2058,"score":2059},"This Warn appears when some other modules uses component with name \"Icon\" (for ex with @iconify or @nuxt/ui)\r\n\r\n\" WARN Overriding Icon component. You can specify a priority option when calling addComponent to avoid this warning. \"\r\n\r\nI supposed it happens somewhere inside nuxt's autoimports behind the scene. Even if i don't use any NuxtUi icons anywhere.\r\nIf i comment @nuxt/icon (or @nuxt/ui) module in nuxt.config.ts - problem dissapears\r\n\r\nProbably for @nuxt/icon would need some prefix or ability to make some prefix when there are several modules with Icon components\r\n\r\nand other thing - this warning doesn't give understanding what should i do exactly ) where i need to \"specify a priority option\" cuz i don't \"calling addComponent\" anywhere directly ))) more questions and no answers )\r\n",[],200,"@nuxt/icon conflicting with @nuxt/ui (and probably with others UI framework which uses \"Icon\" component)","2024-07-18T22:45:12Z","https://github.com/nuxt/icon/issues/200",0.71112907,{"description":2061,"labels":2062,"number":2066,"owner":1988,"repository":2067,"state":2027,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### 🆒 Your use case\n\nThe current Google Analytics registry does not use [consent mode](https://developers.google.com/tag-platform/security/guides/consent?consentmode=advanced). This is used for communicating the user's consent status to Google.\n\n### 🆕 The solution you'd like\n\nI would like to have it as part of the options for the registry script so I can easily define default consent settings as well as the option of opting into consent mode v2.\n\n### 🔍 Alternatives you've considered\n\nCurrently I have opted to just copy the registry script and redefine it with an expanded clientInit property since the default consent needs to be set before `gtag('js', ...)` and `gtag('config', ...)` is called.\r\n\r\n```ts\r\n[...]\r\nclientInit: import.meta.server\r\n ? undefined\r\n : () => {\r\n window.dataLayer = window.dataLayer || []\r\n window.gtag = function () {\r\n // eslint-disable-next-line prefer-rest-params\r\n window.dataLayer.push(arguments)\r\n }\r\n\r\n window.gtag('consent', 'default', {\r\n ad_user_data: 'denied',\r\n ad_personalization: 'denied',\r\n ad_storage: 'denied',\r\n analytics_storage: 'denied',\r\n })\r\n window.gtag('set', { ads_data_redaction: 'true' })\r\n\r\n window.gtag('js', new Date())\r\n window.gtag('config', website.analytics4Key)\r\n },\r\n[...]\r\n```\n\n### ℹ️ Additional info\n\n_No response_",[2063],{"name":2064,"color":2065},"enhancement","a2eeef",243,"scripts","Add consent mode for Google Analytics registry script","2025-02-18T20:30:05Z","https://github.com/nuxt/scripts/issues/243",0.72373265,{"description":2073,"labels":2074,"number":2081,"owner":1988,"repository":2082,"state":2027,"title":2083,"updated_at":2084,"url":2085,"score":2086},"### Environment\r\n\r\nFirefox Browser on Windows\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nText is aggressively wrapped in `\u003Ccode>` blocks inside a table, so the Lifecycle Hooks page is difficult to read.\r\n\r\n\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_",[2075,2078],{"name":2076,"color":2077},"duplicate","cfd3d7",{"name":2079,"color":2080},"responsive","1cd1c6",1400,"nuxt.com","Documentation Lifecycle Hooks code blocks is aggresively wrapped","2023-12-08T15:49:41Z","https://github.com/nuxt/nuxt.com/issues/1400",0.73900294,{"description":2088,"labels":2089,"number":2094,"owner":1988,"repository":2067,"state":2027,"title":2095,"updated_at":2096,"url":2097,"score":2098},"Upgrading to v6.0.2 I get the following errors in the Nuxt Turnstile module:\r\n\r\n```\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(13,17): error TS2742: The inferred type of 'useScriptGoogleTagManager' cannot be named without a reference to '.pnpm/@unhead+vue@1.9.15_vue@3.4.31_typescript@5.5.3_/node_modules/@unhead/vue'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-tag-manager.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(13,17): error TS2742: The inferred type of 'useScriptGoogleAnalytics' cannot be named without a reference to '.pnpm/@unhead+vue@1.9.15_vue@3.4.31_typescript@5.5.3_/node_modules/@unhead/vue'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n.nuxt/nuxt-scripts/tpc/google-analytics.ts(6,7): error TS2742: The inferred type of 'OptionSchema' cannot be named without a reference to '.pnpm/valibot@0.36.0/node_modules/valibot'. This is likely not portable. A type annotation is necessary.\r\n```\r\n\r\nhttps://github.com/nuxt-modules/turnstile/actions/runs/9820960416/job/27116095724?pr=321#step:14:24",[2090,2091],{"name":1999,"color":2000},{"name":2092,"color":2093},"pre-announce","c2e0c6",133,"fix(tpc): a type annotation is necessary","2024-07-15T18:18:26Z","https://github.com/nuxt/scripts/issues/133",0.74005544,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"_lGih5xbGa1moaphWhf7TmzIe0VT4faG_kWQ8YKsEBc":-1},"/nuxt/icon/125"]