I am not sure if this would impact the core system of the Magic Mirror. The feature/change is like this:
The module configuration that is currently being added to the config/config.js could be moved to a file called “module.js” (or some other name) inside the module’s folder, a name that would be static so the core system knows what to look for. When the MagicMirror bootstraps, it would run through all the folders inside the modules subfolder and would load this “module.js” config file and also the other files for the module. This way the custom module would become just a drop-in module with no changes required to the MagicMirror.
The system would detect any modules inside the modules subfolder and would load them, without having to change the config.js.
Is this something that could be done without too much impact in the core of the application? I haven’t looked at JS for a while (java backend developer here), but I can take a look at the source code and come up with a strategy for dynamically loading modules.
(this could be an alternate solutions for: https://forum.magicmirror.builders/topic/17/use-npm-for-module-installs). Less configuration changes in the core system just to install a module.