Recent package rename broke plugin discoverability by Vue CLI

[romansp]

Describe the bug
Package rename from @cnamts/vue-cli-plugin-proxy to vue-cli-proxy-plugin broke plugin discoverability by Vue CLI. All Vue CLI plugins should follow naming convention described here: https://cli.vuejs.org/dev-guide/plugin-dev.html#naming-and-discoverability

vue-cli-plugin-<name> or @scope/vue-cli-plugin-<name>

To Reproduce
Steps to reproduce the behavior:

1. Install vue-cli-proxy-plugin
2. Configure pluginOptions.proxy in vue.config.js
3. Start development server
4. HPM is missing.

Expected behavior
HPM created.

[deraw]

Whoops

I'm sorry, I absolutely didn't thought about this while doing the modification.

I've published a scoped version with the old package name: https://www.npmjs.com/package/@deraw/vue-cli-plugin-proxy

The plugin is again discoverable!

[romansp]

Sorry for posting into closed issue. Is it still possible to update deprecation notice here? https://www.npmjs.com/package/@cnamts/vue-cli-plugin-proxy. So it will produce correct package message in npm/yarn install.

warning @cnamts/vue-cli-plugin-proxy@2.2.1: WARNING: This project has been renamed to vue-cli-proxy-plugin. Install using vue-cli-proxy-plugin instead.

[deraw]

Hi @romansp!

I've updated the deprecation notice on @cnamts/vue-cli-plugin-proxy and I added it to vue-cli-proxy-plugin.

Thank you 🙂