I guess maybe it's better to have the module on the VueUse side. Since we have hundreds of functions and most functions are quite stable, we still expected to see breaking changes because of a few functions in a short amount of time. To archive the experience of "built-in", maybe we could have it inside the starter template so users could have it out-of-box but also have the flexibility to manage the version of VueUse on its own.

The other idea might be we include a very loose version range in dependencies, something like "@vueuse/core": ">=6.0". So that way we could have the latest version available to the newcomers and also not force existing users to upgrade to the least VueUse if any. In this way, we would expect users to always have lock in their project and they can always specify the version of VueUse by explicitly list it as their project dependencies (ideally this might work, just an idea but I haven't see anyone doing that).

Having it in the template or simple command to add seems best option :) It is mostly an extra step when one starts without a template and directly a 2-3 file nuxt 3 project they need one more step which I'm pretty sure we can figure out a way. One idea would be prompting to install as soon as an auto import detected.

I'm not fond of loose version since we will end up depending on implicit node-modules structure and behavior of package managers how they hoist to the top-level. Recreating lock file can also happen for various reasons and they might just face an unwanted upgrade that needs manual addition step.

Closing as we are having the Nuxt module for VueUse now 💚. We could track the auto library discovery and install prompt in another issue.