Support vue 3.x? (different file names)

Following patch tested for vue 3.x, with drush, composer (npm-asset), cloudflare and jsDelivr.

Installation configuration has been changed to use Vue 2 instead of Vue 2.

Please note that Cloudflare links for vue 2 version in current configuration (before changes) does not work.

Also fix some issues, like the _minified_ and _weight_ library options that were applied even if there were no library...

Here is a patch against current release (1.0-rc4).

I've started a 3.x version of this module to handle Vue3 specifically. We'll leave all the Vue2 stuff with the current version.

There's a git branch right now but hopefully I can get a dev release shortly.

Some notable changes at the moment in that 3.x branch

1. No more drush download command. People should use asset-packagist for managing dependencies with composer. Otherwise use a custom CI or npm script to place the library into the right folder. But I could be convinced otherwise if there's a use case.
2. Add the vue recommended default CDN of unpkg
3. Update the CDN locations for jsdelivr and cdnjs
4. Remove vue router (probably reintroduce either a submodule or to the existing config once done refactoring things)
5. Remove vue resource (doesn't appear to be needed for Vue3 nor has a release for it?)
6. Added hook_help info
7. Currently loads the vue runtime and not the global. But we could probably make it a config option.

Thank you very much for your work here @minorOffense! We'll definitely help in the future and with testing!

Re:
1. I'd suggest to use bower-asset instead of npm-asset. At least for us it seems to work better, because it typically only contains the build assets, not the whole src.
Rest: Perfect!

I'd also like to support petite-vue as an option in the future: ✨ Support petite-vue (3.x) Fixed
I think especially for (Drupal) websites that's a super nice match and in many cases better than using the full VueJS.

PS: A good question at this point might be to decide how to provide the different major versions and petite-vue.

I see three possible options:
a) Major release matching the vue version (new one as 3.x of this module)
b) Provide this as master module and submodules per VueJS version. The master module only provides general functionality and the submodules provide the exact versions
c) All into one module, switching versions incl. petite vue by a setting in configuration
d) Split petite-vue into a different module

As I think most of the code is the same for all Vue versions (and petite vue) and the configuration and library logic is most of the work, I'd vote for (b) or (c), tending to (b), as it feels most clean, comfortable to maintain and keep up to date for all versions. (a) would also be fine, if there was only Vue2/3. But I think having petite-vue in the same project would be a real benefit.

Yeah I definitely want to get petite-vue in here too (I have a data table I'd like to make with it). I don't see why we couldn't leave all the base definitions in the one module. Even if we define libraries sites don't need it's not like it'll load them onto a page unless they're requested. I think we're safe enough to just define them all and call it a day. Especially if we're only talking two or maybe three libraries. Anything beyond that and I'd assume whoever's implementing something into their Drupal site will package those assets in their build.

And I was thinking about the "global" vs "runtime" debate and really we should just define whatever library definitions are conceivable and let people use them as needed. If peopel want to bring in vuejs and compile templates on the fly, go for it I guess.

And if we want to set bower as the default that's fine. For some reason I was under the impression bower was not really used anymore (based on https://bower.io/blog/2017/how-to-migrate-away-from-bower/). Either way I'm fine, I just really want people to use composer :-)

Sounds great! I'm also fine with npm-asset, just wanted to let you know about our expeciences with npm vs. bower.

If you give this a first shot, we'll try it out and send feedback!

Quick update, the 3.x branch has the petitie-vue library defined.

@minorOffense as of #13 should this be closed then as it's already solved or which steps are left to be done here?

Thank you very much for your wonderful work!

@minorOffense could you see #14?

What do you think about a stable release for 3.x?

Yes I was actually thinking that. I'm also on my way to VueConf in Toronto later this week. I was gonna roll a stable before going. Hoping to learn a few things to add into the module. Or add some related modules for some common UI elements (like a date picker or something).

Thanks @minorOffense I hope you had great days at VueConf :)

Automatically closed - issue fixed for 2 weeks with no activity.