Extensibility in CLI commands

[fussel178]

Extensibility in CLI commands

Due to the current abstraction process, we need to give the user of the CLI some configuration options back, for example a configuration file where the user can intercept and change something at different stages of CLI runs (especially start and build).

I think, we need intercept points for this parts:

• Craco config
• main process
• IPC manager
• Menu builder
• preload process
• webpack config for main process
• webpack config for preload process
• electron-builder config

in style of:

// telestion.config.js
const { addMenuEntry } = require('@wuespace/telestion-client-cli`);

module.exports = {
  cracoConfig: currentConfig => {
    // change something
    return currentConfig;
  },
  // or
  cracoConfig: () => {
    // I know it better, I do NOT need any default configuration
    // and I am reponsible for any configuration mistakes.
    // build configuration
    return newConfig;
  },
  webpackMain: currentConfig => {...},
  webpackPreload: currentConfig => {...},
  main: (app, mainWindow) => {
    // start something important
  },
  preload: () => {
    // attach something to the preload script
  },
  ipcManager: ipcManager => {
    ipcManager.attachHandler(
      'handleClick',
      () => ipcManager.publish('MY_CHANNEL', 'Hello Renderer!')
    );
  },
  electronMenu: (app, mainWindow, currentMenu, ipcManager) => {
    // add menu entry
    addMenuEntry(currentMenu, 'My awesome menu point', ipcManager.handleClick);
  },
  electronBuilder: currentConfig => {
    // change build target for mac to 'zip' instead of 'default'
    currentConfig.mac.targets = ['zip'];
    return currentConfig;
  }
};

[pklaschka]

Concept for Electron main process injection by JS config files: