\n\u003C/svg>`",[],382,"Some local SVGs cannot be loaded","2025-03-30T07:43:06Z","https://github.com/nuxt/icon/issues/382",0.7431847,{"description":2954,"labels":2955,"number":2963,"owner":2905,"repository":2923,"state":2964,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2956,2959,2960],{"name":2957,"color":2958},"question","d876e3",{"name":2917,"color":2918},{"name":2961,"color":2962},"vue","42b883",3001,"closed","How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.70337135,{"description":2970,"labels":2971,"number":2976,"owner":2905,"repository":2923,"state":2964,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### Description\n\nIf i try to define the position of the notification using the `ui` prop `\u003CUNotifications :ui=\"{position: 'top-0 right-0'}\" />`\r\nthe \"default\" configuration is applied as well (`bottom-0 end-0 `) this happens also if defining the position using the app.config.ts.. I'm assuming i'm doing it wrong.. please advice.. \r\n",[2972,2975],{"name":2973,"color":2974},"duplicate","cfd3d7",{"name":2957,"color":2958},2180,"Notification position","2024-09-11T14:08:24Z","https://github.com/nuxt/ui/issues/2180",0.7275881,{"description":2982,"labels":2983,"number":2987,"owner":2905,"repository":2988,"state":2964,"title":2989,"updated_at":2990,"url":2991,"score":2992},"```\n:resources-blog-list\n\n->\n\n::resources-blog-list\n::\n```\n\nThis should fix the hydration errors",[2984],{"name":2985,"color":2986},"bug","ff281a",587,"nuxt.com","[Content] Replace all inline components in markdown","2023-02-15T12:32:34Z","https://github.com/nuxt/nuxt.com/issues/587",0.7282989,{"description":2994,"labels":2995,"number":2987,"owner":2905,"repository":3002,"state":2964,"title":3003,"updated_at":3004,"url":3005,"score":2992},"After updating to 0.6.10 on Nuht 3 version 3.4.1, i get an error when I try to start\r\n\r\n`\"vitest-environment-nuxt\": \"^0.6.10\"`\r\n\r\n```\r\n❯ yarn test-ui\r\n(node:51339) V8: /Users/ibochkarev/Projects/XXXX/XXXX/node_modules/ttf2woff2/jssrc/ttf2woff2.js:3 Invalid asm.js: Invalid member of stdlib\r\n(Use `node --trace-warnings ...` to show where the warning was created)\r\n\r\n DEV v0.30.1 /Users/ibochkarev/Projects/XXXX/XXXX\r\n UI started at http://localhost:51204/__vitest__/\r\n\r\n\r\n Test Files no tests\r\n Tests no tests\r\n Start at 13:52:13\r\n Duration 368ms (transform 0ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 0ms)\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\nVitest caught 39 unhandled errors 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 Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nDataCloneError: (path) => path.replace(/^\\/oc/, '') could not be cloned.\r\n ❯ new DOMException node:internal/per_context/domexception:72:5\r\n ❯ WorkerInfo.postTask node_modules/tinypool/dist/esm/index.js:421:17\r\n ❯ ThreadPool.runTask node_modules/tinypool/dist/esm/index.js:712:16\r\n ❯ Tinypool.run node_modules/tinypool/dist/esm/index.js:760:38\r\n ❯ runFiles node_modules/vitest/dist/vendor-cli-api.70680cd5.js:7217:20\r\n ❯ node_modules/vitest/dist/vendor-cli-api.70680cd5.js:7254:99\r\n ❯ Object.runTests node_modules/vitest/dist/vendor-cli-api.70680cd5.js:7254:59\r\n ❯ Object.runTests node_modules/vitest/dist/vendor-cli-api.70680cd5.js:7396:5\r\n ❯ async file:/Users/ibochkarev/Projects/umatech/premier.one-v3/node_modules/vitest/dist/vendor-cli-api.70680cd5.js:13913:9\r\n ❯ Vitest.runFiles node_modules/vitest/dist/vendor-cli-api.70680cd5.js:13927:12\r\n ❯ Vitest.start node_modules/vitest/dist/vendor-cli-api.70680cd5.js:13836:5\r\n ❯ startVitest node_modules/vitest/dist/vendor-cli-api.70680cd5.js:20784:5\r\n```\r\n\r\nThis line, which swears at startup, is in nuxt.config.ts config in the proxy section and looks like this\r\n\r\n```js\r\n'/oc': {\r\n target: process.env.NUXT_OC_BACKEND_API_URL,\r\n cookieDomainRewrite: '',\r\n changeOrigin: true,\r\n rewrite: (path: string) => path.replace('/^\\/oc/, '')\r\n },\r\n```\r\n\r\nI tried excluding the config file:\r\n\r\n```js\r\nimport { configDefaults } from 'vitest/config'\r\nimport { defineVitestConfig } from 'nuxt-vitest/config'\r\n\r\nexport default defineVitestConfig({\r\n // any custom vitest config you require\r\n test: {\r\n environment: 'nuxt',\r\n exclude: [...configDefaults.exclude, ['src/shared/api/**', 'public/**', 'node_modules/**', 'nuxt.config.ts']],\r\n },\r\n})\r\n\r\n```\r\n\r\nbut now I get the error\r\n\r\n```\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: pattern.startsWith is not a function\r\n ❯ isNegativePattern node_modules/vitest/dist/vendor-cli-api.70680cd5.js:4702:20\r\n ❯ convertToPositivePattern node_modules/vitest/dist/vendor-cli-api.70680cd5.js:4694:12\r\n ❯ getNegativePatternsAsPositive node_modules/vitest/dist/vendor-cli-api.70680cd5.js:5044:31\r\n ❯ Object.generate node_modules/vitest/dist/vendor-cli-api.70680cd5.js:5004:30\r\n ❯ getWorks node_modules/vitest/dist/vendor-cli-api.70680cd5.js:6957:31\r\n ❯ FastGlob node_modules/vitest/dist/vendor-cli-api.70680cd5.js:6911:19\r\n ❯ WorkspaceProject.globFiles node_modules/vitest/dist/vendor-cli-api.70680cd5.js:13473:12\r\n ❯ WorkspaceProject.globAllTestFiles node_modules/vitest/dist/vendor-cli-api.70680cd5.js:13451:34\r\n ❯ WorkspaceProject.globTestFiles node_modules/vitest/dist/vendor-cli-api.70680cd5.js:13446:34\r\n```",[2996,2999],{"name":2997,"color":2998},"vitest-environment","b60205",{"name":3000,"color":3001},"needs reproduction","DE7793","test-utils","DataCloneError: (path) => path.replace(/^\\/oc/, '') could not be cloned","2023-12-05T11:42:33Z","https://github.com/nuxt/test-utils/issues/587",{"description":3007,"labels":3008,"number":3011,"owner":2905,"repository":2923,"state":2964,"title":3012,"updated_at":3013,"url":3014,"score":3015},"### For what version of Nuxt UI are you asking this question?\n\nv3-alpha\n\n### Description\n\nI'm experience problems with the VS Code Tailwind Intellisense plugin. I have used ui v2 without problems so far, but when using v3 it only shows suggestions when a tailwindcss.config.ts is freshly edited, but then after reloading or restarting VS Code, it doesn't work anymore. When it's working, it only shows a few of the classes, but not the most common ones like padding, margin etc..\n\nHas someone experienced the same issue and knows a fix for that? ",[3009,3010],{"name":2957,"color":2958},{"name":2917,"color":2918},2424,"V3 Intellisense not working correctly","2024-11-05T21:44:20Z","https://github.com/nuxt/ui/issues/2424",0.72870004,["Reactive",3017],{},["Set"],["ShallowReactive",3020],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fRSD4Khgrb5TuXuocThQTCNY--Tppxy1Cg7AdMthWf5A":-1},"/nuxt/ui/3255"]