Open
Description
Describe the bug
headlamp-plugin: npm start puts plugin in wrong folder
Additionally, there should probably be a warning (in headlamp UI and npm start
?) if two of a plugin is added from different folders. The package.json probably has the same name.
TODO: bisect when this changed.
To Reproduce
Steps to reproduce the bug:
- go to a plugin like headlamp-k8s/minikube
npm install
- npm start
- See the plugin is placed in the folder "minikube" not "headlamp-k8s-minikube" as it is when installed via the plugin-catalog.
to test changes to headlamp-plugin
To test in development headlamp-plugin you can do:
cd plugins/headlamp-plugin
npm run build && npm pack
Then within one of the plugins with package.json name == @headlamp-k8s/XXX
do
cd plugins/minikube
npm i ../../headlamp/plugins/headlamp-plugin/kinvolk-headlamp-plugin-0.13.0-alpha.3.tgz
npm start
Then look at the plugin folder (see backend output for where the plugins folder is if you are not running linux):
ls ~/.config/Headlamp/plugins
Metadata
Metadata
Assignees
Type
Projects
Status
Queued