"Configuration file path/to/file/.csscomb.json was not found" reported when JSON is simply not valid

[augbog]

Is there a way we can make it so that if you have invalid JSON, it throws a different error message? It's not a big deal, but thought I should make a mention of it because it is kind of misleading.

Ideally, it should only throw that error if it really does not exist there at all.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5355281-configuration-file-path-to-file-csscomb-json-was-not-found-reported-when-json-is-simply-not-valid?utm_campaign=plugin&utm_content=tracker%2F214563&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F214563&utm_medium=issues&utm_source=github).

[dmnplb]

+1

[istro]

+1.
For me, it was a missing comma between config options generated through the builder tool on the site and "sort-order" copied from a default config file.

[ixley]

+1
New to JSON and tried adding comments. Error message threw me off.