plugin-management: make a library?

[illume]

The plugin-management code is used by the app and headlamp-plugin. However, the previous solution for code sharing didn't work.

So plugin-management was copied into the app/. Temporarily. It was also converted to typescript.

I suggest it is turned into a new package @headlamp-k8s/plugin-management, which can be used by headlamp-plugin and the app/. Probably it should stay in ts.

Acceptance criteria

• PluginManager.list fails if there is no plugins folder headlamp-k8s/plugins@72af907
• PluginManager.list todo headlamp-k8s/plugins@64ad979
• there is a @headlamp-k8s/plugin-management library released that can be used by app/ and headlamp-plugin
• there is documentation on how to make changes to it in development (using npm link or npm pack or whatever)
• there are docs on how to publish it
• installing/removing plugins works in the app
• tests pass (unit tests, and also headlamp-plugin e2e tests)

@yolossn For after the release... What do you think of this proposal?

[yolossn]

Yes, it makes sense to create a new package to avoid code duplication.

[sniok]

This is definitely a good idea.

Probably a little out of the scope of this issue but we have a lot of inter-component dependencies, sometimes we copy, sometimes we use "../". I think we should take an even bigger step and use monorepo tools and separate all reusable parts into packages. This would make our life a lot easier.

Some other cases I can think of:

• headlamp-plugin uses code from frontend, we can extract it into "@headlamp-k8s/headlamp-common" that will have common components and lib
• app uses frontend
• example-plugins use headlamp-plugin