at the moment even in development you make changes to the config.js. These need to be undone before a commit. Also when a user just wants to changes a few settings, he must do so in the original config, leading to a possible merge conflict on the next update.
better might be a user-config.js where you can just add the changes. It should directly overwrite the config.js settings. Chalenge here is to find a way to disable modules.
Other suggestions are welcome
at the moment even in development you make changes to the config.js. These need to be undone before a commit. Also when a user just wants to changes a few settings, he must do so in the original config, leading to a possible merge conflict on the next update.
better might be a user-config.js where you can just add the changes. It should directly overwrite the config.js settings. Chalenge here is to find a way to disable modules. Other suggestions are welcome