@broberg said in Remove module configuration from config/config.js:

however, a “scraper” script would be good for the newbies, i.e a script that scans the modules folder, adds each module and retrieves all config-defaults from each module and puts it all in a new config file.

Thats also an interesting approach and the core system could also monitor the modules folder, so whenever a new module is copied to that folder, the core system would reload the modules or just load the new module and refresh the UI. The same could apply to removing a module, without having to restart the system, if the core detects a folder is not there, it can refresh the UI and remove the module.