chore: ensure '@vueuse/core' is not externalized in tsdown configuration

[chouchouji]

Hi, @rijkvanzanten. I try to run pnpm build and notice that all imports from @vueuse/core is externalized.

I think we should add it to peerDependencies or bundle it in dist. For me, the second choice is best. Maybe some developers don't tend to use this library. We should consider avoiding forcing developers to be limited to a specific library.

You can check the result of incuding @vueuse/core

If you don't think so, just feel free to close this pr. Thanks very much.

[rijkvanzanten]

Hm the downside of that is that the bundle size gets a lot larger for people that do use vue-use already as it's not de-duplicated. I do think it's safe to say this component is generally used within projects that have a bundler themselves as well 🤔

[chouchouji]

Hm the downside of that is that the bundle size gets a lot larger for people that do use vue-use already as it's not de-duplicated. I do think it's safe to say this component is generally used within projects that have a bundler themselves as well 🤔

Yes, I approve it. In order to avoid confusion, we should think to add some tips in readme or just add @vueuse/core to peerDependencies .

[rijkvanzanten]

we should think to add some tips in readme or just add @vueuse/core to peerDependencies .

Lets do that! 🙂