Help new users with config syntax errors, proposal
-
we see a LOT of new users having trouble with unintended syntax errors in config.js.
they don’t know, and MM is running happily without their changes…so, I want to propose adding the call to tests/configs/check_config.js as part of the error handling…
this was easy, except… MM keeps running with the default config… which it shouldn’t…
I’ve tried all kind of things… process.exit(0); is quick death… except the output of the tests/configs/check_config.js isn’t flushed, so the messages don’t show up…
they took out process.stdout.flush() a long time ago…
none of the workarounds appear to work…
anyone got any ideas?
thanks…
