Read the statement by Michael Teeuw here.
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…
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login