\r\n \u003Clabel for=\"checkbox\">{{ checked }}\u003C/label>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\" >\r\n\r\nimport { useLogger } from '@nuxt/kit';\r\nconst { debug } = useLogger();\r\ndebug(\"Bla\");\r\n\r\nconst checked = ref(true);\r\n\r\n\u003C/script>```\n\n### Describe the bug\n\nI have a bigger project and since yesterday I have a lot of problems with the `useLogger` of @nuxt/kit.\r\nI tried to create a more minimal version for reproduction. See above.\r\n\r\nThere is a simple checkbox with a simple label that should change whether is it checked or not (true/false).\r\nAs soon as I add the useLogger import I get the following errror:\r\n`ERROR This module cannot be imported in the Vue part of your app. [importing @nuxt/kit from app.vue]`\r\n\r\nand the checkbox binding no longer works.\r\nComment the three lines, reload and the checkbox binding works again.\r\n\r\n\n\n### Additional context\n\nIn my larger project I get the following:\r\nyarn dev\r\nyarn run v1.22.21\r\n$ nuxt dev\r\nNuxt 3.11.2 with Nitro 2.9.6 \r\n ➜ Local: http://localhost:3000/\r\n ➜ Network: use --host to expose\r\n\r\n ➜ DevTools: press Shift + Option + D in the browser (v1.3.2) \r\n ERROR This module cannot be imported in the Vue part of your app. [importing @nuxt/kit from src/pages/[uuid].vue] \r\n ERROR This module cannot be imported in server runtime. [importing @nuxt/kit from src/server/api/details/[uuid].ts] \r\nℹ Vite server warmed up in 2396ms \r\n ERROR This module cannot be imported in server runtime. [importing node_modules/@nuxt/kit/dist/index.mjs from src/server/routes/[uuid]/result.ts]\r\n\r\n✔ Nuxt Nitro server built in 1414 ms nitro\r\n\r\n ERROR [worker reload] [worker init] The requested module 'file:///Users/wdittmer/xxx/frontend/node_modules/unenv/runtime/mock/proxy.cjs' does not provide an export named 'useLogger' \r\n\r\n import { useLogger as useLogger$1 } from 'node_modules/unenv/runtime/mock/proxy.cjs';\r\n ^^^^^^^^^\r\n SyntaxError: The requested module 'node_modules/unenv/runtime/mock/proxy.cjs' does not provide an export named 'useLogger'\r\n at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)\r\n at async ModuleJob.run (node:internal/modules/esm/module_job:191:5)\r\n at async ModuleLoader.import (node:internal/modules/esm/loader:336:24)\r\n at async loadESM (node:internal/process/esm_loader:34:7)\r\n at async handleMainPromise (node:internal/modules/run_main:106:12)\r\n \r\n \r\n \r\n Env:\r\n ------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.19.1\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: experimental, srcDir, ignore, css, app, runtimeConfig, build, modules, security, vite\r\n- Runtime Modules: nuxt-security@0.14.4\r\n- Build Modules: -\r\n------------------------------\n\n### Logs\n\n```shell-script\nERROR This module cannot be imported in the Vue part of your app. [importing @nuxt/kit from app.vue]\n```\n",[2903,2906],{"name":2904,"color":2905},"3.x","29bc7f",{"name":2890,"color":2891},27408,"This module cannot be imported in the Vue part of your app. [importing @nuxt/kit from app.vue] causing page to not work","2024-06-03T17:32:32Z","https://github.com/nuxt/nuxt/issues/27408",0.7140582,{"description":2913,"labels":2914,"number":2926,"owner":2866,"repository":2866,"state":2881,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, modules, typescript\r\n- Runtime Modules: @nuxtseo/module@2.0.0-beta.15\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n- minimal changes to nuxt config adding `typeCheck: true` and `compilerOptions.noUncheckedIndexedAccess: true`\r\n\r\nhttps://stackblitz.com/edit/github-vdxk2t?file=nuxt.config.ts\r\n\r\n### Describe the bug\r\n\r\nThis highlights an issue when trying to use tsconfig features e.g. `noUncheckedIndexedAccess` or `noUnusedLocals` etc. in a nuxt project to provide stricter code conformance. Any nuxt module you have installed will also be checked for these same rules.\r\n\r\nThis effectively means you cannot use any of the tsconfig rules for the risk of a module developer not adhering to those same standards.\r\n\r\nNuxt should not be type checking any installed modules as part of build with the same tsconfig rules defined at the project level. Providing access to all tsconfig properties is misleading as they effectively don't work with the nuxt ecosystem unless you have a raw project.\r\n\r\nThe repro and logs below show how this fails for the `@nuxtseo/module` module but this error is present in a number of modules I have tried to use e.g. `content`\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nERROR 21:54:09\r\n ERROR(vue-tsc) Type '{ icon: string; label: false; ariaLabel: string | undefined; current?: boolean | undefined; disabled?: boolean | undefined; to?: string | undefined; separator?: string | undefined; hideSeparator?: boolean | undefined; ui?: { ...; } | undefined; }' is not assignable to type 'BreadcrumbItemProps'.\r\n Types of property 'to' are incompatible.\r\n Type 'string | undefined' is not assignable to type 'string'.\r\n Type 'undefined' is not assignable to type 'string'.\r\n FILE /home/projects/github-vdxk2t/node_modules/nuxt-seo-ui/dist/runtime/components/Breadcrumb.vue:46:5\r\n\r\n 44 | }\r\n 45 | if (props.homeIcon) {\r\n > 46 | items[0] = {\r\n | ^^^^^^^^\r\n 47 | ...items[0],\r\n 48 | icon: 'material-symbols:home-outline-rounded',\r\n 49 | label: false,\r\n\r\n[vue-tsc] Found 1 error. Watching for file changes. (x3)\r\n```\r\n```\r\n",[2915,2918,2921,2922,2923],{"name":2916,"color":2917},"discussion","538de2",{"name":2919,"color":2920},"types","2875C3",{"name":2904,"color":2905},{"name":2857,"color":2858},{"name":2924,"color":2925},"🔨 p3-minor","FBCA04",23609,"`typeCheck` reports errors from modules when using `tsconfig` rules","2023-11-30T07:26:56Z","https://github.com/nuxt/nuxt/issues/23609",0.71477556,{"description":2932,"labels":2933,"number":2937,"owner":2866,"repository":2867,"state":2881,"title":2938,"updated_at":2939,"url":2940,"score":2941},"Related #196 \n\n| Alias | Name | Version |\n| ----- | ------------------------------------------- | --------------- |\n| ui | [nuxt/ui][nuxt-ui-href] | v3.0.0-alpha.10 |\n| tw | [tailwindcss][tailwindcss-href] | v4.0.0-beta.8 |\n| tv | [tailwind-variants][tailwind-variants-href] | v0.3.0 |\n| tm | [tailwind-merge][tailwind-merge-href] | v2.6.0 |\n| uno | [unocss][unocss-href] | v0.65.3 |\n\n**ui internally uses tv to flexibly generate component class names. tv internally uses tm to merge classes with the same effect (e.g., `p-2 p-4` --> `p-4`), and finally uses tw to recognize class names and generate style classes.**\n\n**After examining tv and tm, it became apparent that they don't strongly depend on tw, which opens up the possibility of replacing the final style generation step with uno.**\n\n\u003Cdetails>\n\u003Csummary>## tw Prefix Attempt (Optional)\u003C/summary>\n\nInitially, the idea was to limit tw to ui internals and uno for user usage. With tw's [prefix][tw-prefix-href] feature, the class rules became simpler. **However, ui internally (v3.0.0-alpha.10) doesn't yet support passing tw prefix configuration**, so let's first make ui support tw prefixes.\n\n### Understanding tv Variants\n\nTo add prefixes, we need to analyze the data structure that tv accepts.\n\n#### Regular Variants\n\n```ts\n import { tv } from 'tailwind-variants';\n\n tv({\n variants: {\n foo: {\n foo_val: 'px-2', // or ['pxx-2', ...], be the same, class / className\n },\n }\n })({ foo: 'foo_val' })\n```\n\n#### Boolean Variants (Including true/false keys)\n\n```ts\n tv({\n variants: {\n foo: {\n true: 'px-2',\n false: 'py-2',\n }\n }\n })({ foo: true, })\n```\n\n#### Compound Variants (Intersection between variants)\n\n```ts\n tv({\n variants: {\n foo: {\n foo_val: 'px-2',\n foo_val2: 'px-2',\n },\n bar: {\n true: 'px-2',\n false: 'py-2',\n },\n },\n compoundVariants: [\n {\n foo: 'foo_val', // or ['foo_val', 'foo_val2', ]\n bar: true,\n class: 'text-white', // You can also use \"className\" as the key\n }\n ],\n })({ foo: true, })\n```\n\n#### Responsive Variants (Device screen sizes)\n\n```ts\n tv({\n variants: {\n foo: {\n foo_val: 'px-2',\n foo_val2: 'px-4',\n },\n }\n },\n {\n responsiveVariants: ['sm', 'md'] // or `true` for all\n })({ \n foo: {\n initial: 'foo_val',\n sm: 'foo_val',\n md: 'foo_val2',\n }\n })\n```\n\n#### Slot Variants (Combining above variants with slots)\n\n```ts\n tv({\n slots: {\n slot_a: 'mx-2',\n slot_b: 'mx-2',\n },\n compoundSlots: [\n {\n slots: ['slot_a', 'slot_b', ], \n class: '',\n foo: 'foo_val', // for all slot while variant is missing\n },\n ],\n variants: {\n foo: {\n foo_val: {\n slot_a: 'px-2',\n }\n },\n bar: {\n true: {\n slot_a: 'mx-2'\n },\n false: {\n slot_a: 'mx-0'\n },\n },\n },\n compoundVariants: [\n {\n foo: 'foo_val',\n bar: true,\n class: {\n slot_a: '',\n }\n }\n ],\n {\n responsiveVariants: ['sm', 'md'] // or `true` for all\n }\n })({ \n foo: {\n initial: 'foo_val',\n sm: 'foo_val',\n md: 'foo_val2',\n }\n }) // --> { foo_slot, bar_slot, }\n```\n\n### Summary\n\nAfter adding prefix functionality locally (#3009 ) and configuring tw prefix (while installing uno to handle non-prefix classes in the playground for page styling), **practical usage revealed some unavoidable conflicts, such as at-rule usage. Additionally, this approach doesn't effectively prevent files from being processed twice (by both tw & uno)**. Therefore, let's try a different approach: remove tw completely and use UnoCSS for everything!\n\n\u003C/details>\n\n## Modifying ui\n\n### Disabling tw Plugin\n\nRemove `@tailwindcss/vite` installation handling from ui internals.\nRemove tw imports and specific configurations from ui playground.\n\n### Introducing uno\n\nFor [nuxt](https://unocss.dev/integrations/nuxt) | [vite](https://unocss.dev/integrations/vite)\n\nAlso, [Style Reset](https://unocss.dev/guide/style-reset) can be applied as needed.\n\n**IMPORTANT: Include @nuxt/ui files**\n\n```ts\nexport default defineConfig({\n presets: [\n presetUno(),\n ],\n content: {\n pipeline: {\n include: [\n // the default\n /\\.(vue|svelte|[jt]sx|mdx?|astro|elm|php|phtml|html)($|\\?)/,\n // IMPORTANT include @nuxt/ui files\n /\\.nuxt\\/ui\\//,\n ]\n }\n }\n})\n```\n\n## Primitive Variables\n\nuno doesn't generate primitive variables like tw does (e.g., `--color-green-500`, `--text-lg`, `--radius-md`, etc.), but ui internally needs these variables.\n\n**For now, we'll directly copy the primitive variables from tw's normal loaded to local.**\n\n## Rule Inconsistencies\n\n**There are must more undiscovered issues**\n\n### Ring\n\nIn uno, the default `ring` width is 3px, different from tw's 1px.\n\n**Solution:**\n\n```ts\n shortcuts: {\n ring: 'ring-1'\n },\n```\n\n### Color Opacity\n\ntw internally uses [color-mix](https://developer.mozilla.org/zh-CN/docs/Web/CSS/color_value/color-mix), allowing direct opacity settings for color variables.\nCurrently, uno doesn't support this directly.\n\ntw: `class=\"bg-[var(--color-primary)]/20\"` ✓\nuno: `class=\"bg-[var(--color-primary)]/20\"` ✕\nuno: `class=\"bg-[rgb(255,5,5)]/20\"` ✓\n\n```css\n:root {\n --color-primary: rgb(255, 5, 5);\n}\n```\n\nAfter observing ui usage, uno rules were added:\n\nuno: `class=\"bg-[var(--ui-primaey)]/20\"` ✓\nuno: `class=\"hover:bg-[var(--ui-primaey)]/75\"` ✓\n\n**Solution:**\n\n```ts\n rules: [\n [/(?:([^:\\s]+):)?bg-.*?\\[(var\\(--[^-]+-[^)]+\\))\\]\\/(\\d+)/, function* ([, modifier, color, alpha], { symbols }) {\n yield {\n background: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n if (modifier) {\n yield {\n [symbols.selector]: selector => `${selector}:${modifier}`,\n background: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n }\n }],\n [/(?:([^:\\s]+):)?text-.*?\\[(var\\(--[^-]+-[^)]+\\))\\]\\/(\\d+)/, function* ([, modifier, color, alpha], { symbols }) {\n yield {\n color: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n if (modifier) {\n yield {\n [symbols.selector]: selector => `${selector}:${modifier}`,\n color: `color-mix(in oklab, ${color} ${alpha}%, transparent)`\n }\n }\n }]\n ],\n```\n\n---\n\nNow, let's run the playground! ~\n\n## Notes\n\n### tm's handling of tw and uno exclusive rules yields unexpected results\n\ntw doesn't directly support units (px, em, ...) like `text-Xpx`, requiring `text-[Xpx]` instead.\n\n- `text-md text-[20px]` --> `text-[20px]`\n- `text-md text-20px` --> `text-md text-20px`\n- `text-16px text-20px` --> `text-20px`\n- `text-[16px] text-[20px]` --> `text-[20px]`\n\n**When using ui, it's recommended to pass classes that tw can also parse.**\n\n[Commits · byronogis/ui](https://github.com/byronogis/ui/commits/test/use-unocss/)\n\n---\n\n\n[nuxt-ui-href]: https://ui3.nuxt.dev\n[tailwindcss-href]: https://tailwindcss.com/docs/v4-beta\n[tailwind-variants-href]: https://www.tailwind-variants.org/\n[tailwind-merge-href]: https://github.com/dcastil/tailwind-merge\n[unocss-href]: https://unocss.dev/\n[tw-prefix-href]: https://tailwindcss.com/docs/v4-beta#using-a-prefix\n",[2934],{"name":2935,"color":2936},"question","d876e3",3011,"[Attempt] Exploring the Coexistence of Nuxt UI v3 and UnoCSS","2025-05-10T19:47:10Z","https://github.com/nuxt/ui/issues/3011",0.71902347,{"description":2943,"labels":2944,"number":2947,"owner":2866,"repository":2866,"state":2881,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Environment\r\n\r\n- Operating System: windows10\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.8.2\r\n- vue: 3.3.10\r\n- vue-router: 4.2.5\r\n- Package Manager: npm@10.2.3\r\n\r\n### Reproduction\r\n\r\n复现地址:https://stackblitz.com/edit/github-hi9xzq?file=app.vue,pages%2Findex.vue,pages%2Ftest.vue\r\n\r\n### Describe the bug\r\n\r\n### 这个Index组件beforeRouteEnter钩子函数在浏览器刷新页面的时候未执行nuxt传入的回调函数,正常的nuxt-link组件跳转就会正常执行。\r\n```\r\n\r\n\u003Cscript lang=\"tsx\">\r\nexport default defineComponent({\r\n name: 'Index',\r\n beforeRouteEnter(to, form, next) {\r\n console.log({ to, form, next })\r\n return next(vm => {\r\n console.log({ vm })\r\n })\r\n },\r\n setup() {\r\n return () => (\r\n \u003Cdiv>\r\n \u003Cdiv>Index\u003C/div>\r\n \u003Cnuxt-link to=\"/test\">Text\u003C/nuxt-link>\r\n \u003C/div>\r\n )\r\n }\r\n})\r\n\u003C/script>\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_\n```[tasklist]\n### Tasks\n```\n",[2945,2946],{"name":2904,"color":2905},{"name":2890,"color":2891},24989,"nuxt3 的tsx组件中beforeRouteEnter感觉有怪异的情况","2024-01-02T04:51:38Z","https://github.com/nuxt/nuxt/issues/24989",0.7191214,{"labels":2953,"number":2956,"owner":2866,"repository":2866,"state":2881,"title":2957,"updated_at":2958,"url":2959,"score":2960},[2954,2955],{"name":2890,"color":2891},{"name":2893,"color":2894},7792,"Non-posix ignore patterns are given to globby on win32 with new `nuxt generate` cache feature","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7792",0.720949,{"description":2962,"labels":2963,"number":2966,"owner":2866,"repository":2866,"state":2881,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.4.1`\r\n- Nitro Version: `2.3.3`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `app`, `css`, `components`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\npage/[...id].vue\r\n\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ccomponent\r\n v-for=\"(item, key) in data\"\r\n :key=\"key\"\r\n :is=\"item.type\" \r\n \r\n v-bind=\"item\"\r\n\r\n @lgc-action=\"$emit($event.handler, $event)\"\r\n\r\n\r\n @update:payload=\"(value) => item.payload = value\"\r\n @update:form=\"(value) => item.form = value\"\r\n @update:restriction=\"(value) => item.restriction = value\"/>\r\n \r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n\r\n const route = useRoute()\r\n const runtimeConfig = useRuntimeConfig()\r\n const [path] = route.params.id.slice(-1)\r\n const { data } = reactive(await $fetch(`${runtimeConfig.public.BASE_URL}${runtimeConfig.public.SERVICE}/web/portal/${runtimeConfig.public.POI_NAME}/form/${path}`))\r\n \r\n\u003C/script>\r\n```\r\n\r\n\r\ncomponent/form.vue\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"lgc-form-input-group\">\r\n \u003Cp v-if=\"label\" class=\"lgc-form-input-group__label\">{{ label }}\u003C/p>\r\n \u003Cdiv class=\"lgc-form-input-group__form\">\r\n \u003C!-- v-bind=\"!item.type.toLowerCase().includes('form') ? { data: item } : item\" -->\r\n \u003Ccomponent :attr=\"index\" v-for=\"(item, index) in data\" :key=\"index\" :is=\"item.type\" v-bind=\"item\" \r\n @update:isValid=\"item.isValid = $event\"\r\n @emit-value=\"constructPayload(item, $event)\"\r\n @emit-input-and-value=\"constructPayload($event.input, $event.payload)\"\r\n @add-error=\"errorManagement('add', $event)\"\r\n @remove-error=\"errorManagement('remove', $event)\"\r\n @lgc-action=\"$emit($event.handler, $event)\"\r\n >\u003C/component>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nimport { v4 as uuidv4 } from 'uuid';\r\n\r\nconst emit = defineEmits(['emit-value','lgc-action'])\r\n\r\nconst props = defineProps({\r\n data: {\r\n type: Array,\r\n required: true\r\n },\r\n id: {\r\n type: String,\r\n required: false\r\n },\r\n label: {\r\n type: String,\r\n required: false\r\n },\r\n value: {\r\n type: Object,\r\n required: false,\r\n default() {\r\n return {}\r\n }\r\n },\r\n uuid: {\r\n type: String,\r\n required: false,\r\n default() {\r\n return uuidv4()\r\n }\r\n }\r\n })\r\n\r\n\r\n const inputValue= reactive(props.value ? props.value : {})\r\n\r\n function constructPayload(input, payload) {\r\n inputValue[input.id] = payload\r\n }\r\n\r\n function errorManagement(action, error) {\r\n let component = props.data.find(el => el.type === 'lgc-form-error');\r\n if (component) {\r\n let already = component.errors.find(el => el.key === error.key && el.byClient)\r\n let index = component.errors.indexOf(already)\r\n switch (action) {\r\n case 'add':\r\n if (component) {\r\n if (already) component.errors.splice(index, 1)\r\n if (error.value) component.errors.push(error)\r\n }\r\n break;\r\n case 'remove':\r\n if (component) {\r\n if (already) component.errors.splice(index, 1)\r\n }\r\n break;\r\n default:\r\n break;\r\n }\r\n } else {\r\n emit(`${action}-error`, error)\r\n }\r\n }\r\n\r\n async function submit() {\r\n emit('emit-value', inputValue)\r\n }\r\n\r\n\u003C/script>\r\n\r\n```\r\n\r\n### Describe the bug\r\n\r\nThe problem occurred when switching from nuxt2 to nuxt3.\r\nthis is a problem with the display order of compose with the `\u003Ccomponent :is=\"\" v-for=\"\" :key=\"\">` tag, in all that I find as documentation, it tells me offers 2 solutions:\r\n- make a sort function but even then, it doesn't work\r\n- that it is an asynchronous problem and must be made synchronous. Off, nuxt3 with \u003Cscript setup> makes compose directly asynchronous. It would then possibly be a \"bug\" linked to the frame work.\r\n\r\nafterwards, I haven't seen any documentation on the problem caused here: depending on the index, the order changes.\r\nIn addition to the tests you had done, I tried to put a uuid in key, the whole display is reversed.\r\nwithout key, it's good\r\nthe index, gives the current problem\r\na fixed key or just the item gives an even different display.\r\nregarding the key, ideally, the uuid should be in the object since using the index seems to be a bad practice\r\n \r\n The problem occurs in the compose form\r\n \r\n result nuxt 2 & nuxt3 no :key\r\n\u003Cimg width=\"701\" alt=\"Capture d’écran 2023-04-26 à 10 51 51\" src=\"https://user-images.githubusercontent.com/98752049/234523209-431b7cfc-d0c0-4397-a82d-d6120635a12a.png\">\r\n\r\nresult nuxt 3 whit :key=\"index\"\r\n\u003Cimg width=\"675\" alt=\"Capture d’écran 2023-04-26 à 10 55 16\" src=\"https://user-images.githubusercontent.com/98752049/234524004-76a98dde-1312-4266-9455-d9f28c1c521d.png\">\r\n\r\nresult nuxt3 whit :key=\"uuidv4()\"\r\n\u003Cimg width=\"678\" alt=\"Capture d’écran 2023-04-26 à 10 57 25\" src=\"https://user-images.githubusercontent.com/98752049/234524648-d85ae34d-70b5-4f58-a23d-005e8afd829a.png\">\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_",[2964,2965],{"name":2904,"color":2905},{"name":2890,"color":2891},20522,"Nuxt2 to Nuxt3, not display component in a correct order ","2023-04-26T09:06:18Z","https://github.com/nuxt/nuxt/issues/20522",0.7215107,{"labels":2972,"number":2977,"owner":2866,"repository":2866,"state":2881,"title":2978,"updated_at":2979,"url":2980,"score":2981},[2973,2975,2976],{"name":2974,"color":2864},"stale",{"name":2890,"color":2891},{"name":2893,"color":2894},10165,"Nuxt is removing universal selectors from css","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10165",0.72179574,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBoow4DSgwyqpIIGJ_TlrjrCfgPO3F12qLO3IvcB8SXk":-1},"/nuxt/ui/4090"]