The configuration examples are not valid JSON, due to trailing commas. Not a great first impression. https://github.com/runreveal/kawa#getting-started

I see it's because they use their own config loader library that uses hujson. Why even use the human-unfriendly JSON format if you're also going to make it machine-unfriendly by not conforming? If nothing else, why not at least acknowledge that in the documentation which still calls it JSON? If this is what Grug Brained development looks like, they can keep it.