Current situation
Right now the plugins can either be developed inside the frontend (in frontend/src/plugin/plugins) or outside which is the recommended way to then ship it externally. The recommended option however, makes for a complicated developer experience, as it's complicated to continuously verify/reload any changes to plugins externally.
Impact
This makes developing plugins a bit clunkier/harder than it should.
Ideal future situation
Developers can continuous develop plugins: see their changes hot-reloaded and extract the plugins into a bundle when ready.
Implementation options
1) Develop the plugins inside Headlamp's frontend and extract them (into their own bundle) with an easy command;
or 2) Headlamp has a way to import unbundled plugins and hot-reload any changes to them.
Current situation Right now the plugins can either be developed inside the frontend (in frontend/src/plugin/plugins) or outside which is the recommended way to then ship it externally. The recommended option however, makes for a complicated developer experience, as it's complicated to continuously verify/reload any changes to plugins externally.
Impact This makes developing plugins a bit clunkier/harder than it should.
Ideal future situation Developers can continuous develop plugins: see their changes hot-reloaded and extract the plugins into a bundle when ready.
Implementation options 1) Develop the plugins inside Headlamp's frontend and extract them (into their own bundle) with an easy command; or 2) Headlamp has a way to import unbundled plugins and hot-reload any changes to them.