Joaquín Sánchez

Maybe you can use `basename(filename, extname(filename))` instead regexp. Anyway, you sould use kebab or camel case for the file names.

https://youtrack.jetbrains.com/issue/WEB-52214/Support-auto-importing-source-components-in-project-with-vite-plugin-components-and-unplugin-vue-components

No, I just file a new issue to include support in JetBrains IDE, for example rigth now we can run Vitest tests, a few months ago there wasn't support.

> 另外好像还有个问题，引入标签时，他好像还会自动import yes, just remove added import(s), same problem when using auto imported composables

Right now there is an alternative using `custom` and default slot props, but requires wrapping the component, for example: ```html Link

> Router-link is available in nuxt right? How does using this instead behave differently? Both are there, this PR should be changed to allow render `RouterLink` and `NuxtLink` (v2 behavior):...

Sorry for the confusion: This PR was about adding `NuxtLink:useLink` support from Nuxt issue (the releated issue here was mentioned there, but it is not related): Nuxt issue is about...

Any ssr page should also be excluded using `navigateFallbackDenylist`: check https://github.com/vite-pwa/sveltekit/issues/65 for more details Check also this PR https://github.com/vite-pwa/nuxt/pull/108

`Masquerading as ESM error` should be fixed in the package exports in the target library, the problem is about dual CJS/ESM package exports with default exports, the generated cjs module...

Related kit changes: - https://github.com/sveltejs/kit/pull/5416 - https://github.com/sveltejs/kit/pull/5620 - https://github.com/sveltejs/kit/pull/5601#issuecomment-1188391404