I notice you renamed the plugin and that's fine, but you should remove the old one from npm, and moreover from the vue cli-3 plugin search functionality (specifically with the vue ui).
In the vue ui there are both version (pages and multipages), and the plugin with more installations is the multipages (the plugins are identical btw). People are more inclined to install the version with more download, and if so, and they are following the instruction in your github page, they will soon find an error when they launch the server. The multipages is built to require a multipages logger, and instead the plugin on github requires a pages logger. In this acse compilation fails, and that just create confusion, and often the abandon of the plugin.
To avoid all this just remove the old version everywhere, and leave around just one version (pages).
I wanna remove the old one, but i can't.It seems that the only thing i can do is to deprecate it by npm deprecate vue-cli-plugin-multipages and now it was done.
I notice you renamed the plugin and that's fine, but you should remove the old one from npm, and moreover from the vue cli-3 plugin search functionality (specifically with the vue ui).
In the vue ui there are both version (pages and multipages), and the plugin with more installations is the multipages (the plugins are identical btw). People are more inclined to install the version with more download, and if so, and they are following the instruction in your github page, they will soon find an error when they launch the server. The multipages is built to require a multipages logger, and instead the plugin on github requires a pages logger. In this acse compilation fails, and that just create confusion, and often the abandon of the plugin.
To avoid all this just remove the old version everywhere, and leave around just one version (pages).
Thanks btw for the plugin.