\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vT9fUh9cK0d\n\nAfter change `1` transforms to `\"1\"` and got error in console.",[3081,3084,3087],{"name":3082,"color":3083},"bug","d73a4a",{"name":3085,"color":3086},"duplicate","cfd3d7",{"name":3051,"color":3052},2886,"USelect converts integer value to string","2025-01-09T14:22:11Z","https://github.com/nuxt/ui/issues/2886",0.70659995,{"description":3094,"labels":3095,"number":3102,"owner":3022,"repository":3054,"state":3039,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Description\n\nThe [documentation](https://ui.nuxt.com/components/date-picker) uses v-calendar as an example to create a date picker component. However, v-calendar is likely abandoned and will no longer be maintained (see https://github.com/nathanreyes/v-calendar/issues/1503 ) . Latest release was over a year ago.\n\nAlso, it has a dependency on a vulnerable lodash version ( see https://github.com/nathanreyes/v-calendar/issues/1420 ).\n\nWhat other alternatives are you planning on using in your documentation, or are there any other examples using a different library?\n\nThanks.",[3096,3099],{"name":3097,"color":3098},"question","d876e3",{"name":3100,"color":3101},"wontfix-v2","ffffff",3239,"DatePicker documentation uses library that's no longer maintained","2025-02-04T20:40:38Z","https://github.com/nuxt/ui/issues/3239",0.70955175,{"description":3108,"labels":3109,"number":3112,"owner":3022,"repository":3022,"state":3039,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Environment\n\nNuxi 3.0.0-rc.10-27707547.a4fa070 \n\n### Reproduction\n\n1. Install the [Vite Vue Inspector plugin](https://github.com/webfansplz/vite-plugin-vue-inspector)\r\n2. npm run dev\n\n### Describe the bug\n\nThe following error message shows up:\r\n\r\n[vite] Internal server error: ENOENT: no such file or directory, open 'C:\\ . . . \\node_modules\\vite-plugin-vue-inspector\\src\\load.js?v=707afc2d'\r\n\r\nHowever, clicking on the link in VSCode does open the file so the file under the specified path exists.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3110,3111],{"name":3032,"color":3033},{"name":3019,"color":3020},14829,"Error saying \"no such file or directory\" from nuxt.config.ts when file exists","2023-01-19T17:41:00Z","https://github.com/nuxt/nuxt/issues/14829",0.71036357,{"description":3118,"labels":3119,"number":3123,"owner":3022,"repository":3022,"state":3039,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.12.2\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: default\n- Runtime Modules: subpath-demo/mod\n- Build Modules: -\n\n### Reproduction\nhttps://codesandbox.io/p/devbox/bold-moon-4f3lll?workspaceId=02247d38-3c4c-4910-9e35-fabf9385962a\n\n[module's code](https://github.com/shunnNet/demo-nuxt-module-subpath-issue)\n\n### Describe the bug\n\nA Nuxt module can be installed via a package subpath, which allows it to differ from the actual directory structure, such as:\n\n```json\n{\n \"exports\": {\n \"./mod\": {\n \"types\": \"./packages/mod/dist/types.d.ts\",\n \"import\": \"./packages/mod/dist/module.mjs\",\n \"require\": \"./packages/mod/dist/module.cjs\"\n }\n }\n}\n```\n\nWhen installed through this subpath, although the module was successfully installed, the Nuxt module's runtime code (e.g: Nuxt plugin) encounters errors when import from aliases e.g: `#app`. \n\n```ts\nexport default defineNuxtConfig({\n // omit\n modules: [\n \"subpath-demo/mod\"\n ],\n})\n```\n\n```ts\nimport { defineNuxtPlugin } from \"#app\"; // \u003C--- will fail\nexport default defineNuxtPlugin((_nuxtApp) => {\n console.log(\"Plugin injected by my-module!\");\n});\n```\n\nThis may be related to how Vite `ssr.noExternal` is configured. \n\nCurrently, Nuxt directly sets it to the user-provided string (`subpath-demo/mod`), but imports plugins using the full absolute path. ( `..... /node_modules/subpath-demo/packages/mod/dist/module.mjs`), which is not match. And dependencies will be externalized by Vite if it wasn't included in `ssr.noExternal`. [vite ssr-external](https://vite.dev/guide/ssr.html#ssr-externals)\n\nTherefore, when the subpath differs from the actual path, Vite excludes it from compilation.\n\n\n## Workaround\n1. Align subpath with actual path\n\n2. Manually add package name to `ssr.noExternal`\n\n```ts\nexport default defineNuxtConfig({\n // omit\n modules: [\n \"subpath-demo/mod\"\n ],\n vite: {\n ssr: { \n noExternal: [ \"subpath-demo\" ] \n }\n }\n})\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n```\nERROR [nuxt] [request error] [unhandled] [500] Package import specifier \"#app\" is not defined in package /Users/net/repository/test-mod-dep/node_modules/.pnpm/subpath-demo@https+++codeload.github.com+shunnNet+demo-nuxt-module-subpath-issue+tar.gz+f5f70_gfo3iqyqpkpaqjbz4jtbsmbv6e/node_modules/subpath-demo/package.json imported from /Users/net/repository/test-mod-dep/node_modules/.pnpm/subpath-demo@https+++codeload.github.com+shunnNet+demo-nuxt-module-subpath-issue+tar.gz+f5f70_gfo3iqyqpkpaqjbz4jtbsmbv6e/node_modules/subpath-demo/packages/mod/dist/runtime/plugin.js\n at importNotDefined (node:internal/modules/esm/resolve:291:10) \n at packageImportsResolve (node:internal/modules/esm/resolve:741:9) \n at moduleResolve (node:internal/modules/esm/resolve:917:16) \n at defaultResolve (node:internal/modules/esm/resolve:1157:11) \n at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:390:12) \n at ModuleLoader.resolve (node:internal/modules/esm/loader:359:25) \n at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:234:38) \n at ModuleWrap.\u003Canonymous> (node:internal/modules/esm/module_job:87:39) \n at link (node:internal/modules/esm/module_job:86:36)\n```",[3120,3121],{"name":3082,"color":3083},{"name":3122,"color":3037},"🔨 p3-minor",29735,"Occur error when module path is a package subpath that does not match the actual path","2024-12-03T13:20:01Z","https://github.com/nuxt/nuxt/issues/29735",0.7120218,{"description":3129,"labels":3130,"number":3133,"owner":3022,"repository":3054,"state":3039,"title":3134,"updated_at":3135,"url":3136,"score":3137},"### Description\n\nNuxt UI should have the potential to open native links in a Nuxt UI Modal by simply adding a certain `modal` parameter in [NuxtLink](https://nuxt.com/docs/api/components/nuxt-link).\n\n`\u003CNuxtLink to=\"/about\" modal>About page shown in modal but can also be opened natively (e.g. new tab)\u003C/NuxtLink>`\n\nThe link should still be a native link with progressive enhancement, so _if users would like to open the URL in a new tab, they can do_! If not, it will open the content in a modal.\n\nThat would be great DX and UX! 🎉\n\nThe `modal` property is just one possible solution, maybe there's even a better one using a native HTML property like `rel=\"modal\"`, we should discuss that.\n\nIn future versions there might be further control parameters to override the defaults for\n\n- modal size\n- modal style\n- modal opacity\n- ...\n\nBut let's start simple.\n\nSomething similar was done here, but I think this should really be part of Nuxt UI or even Nuxt Core.\nhttps://nuxt-pages-plus.pages.dev/components/plus-modal-link\n\n### Additional context\n\n_No response_",[3131,3132],{"name":3048,"color":3049},{"name":3051,"color":3052},3298,"Enhance NuxtLink to open in Modal using a \"modal\" property","2025-03-08T12:21:53Z","https://github.com/nuxt/ui/issues/3298",0.71283805,["Reactive",3139],{},["Set"],["ShallowReactive",3142],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ffPRinqKhA80xy7hHy7QmKTVqydQmwuJ22IwMbxWYp2U":-1},"/nuxt/scripts/15"]