That would be a pretty big mistake for the author of both the JSON spec and JSMin to make? Maybe it is but it seems unlikely.
JSMin is not the right tool for this. I'm sure it conforms to the JavaScript (ECMAScript) spec but probably not the JSON spec. Here's a trivial JavaScript function to convert JSON5 to regular JSON with no comments and quoted identifiers and all that good stuff:
function JSON5_to_JSON(str) {
return JSON5.parse(str).stringify();
}
This is exactly what is suggested in the Usage section of the linked article.
If the author of the JSON spec and JSMin says it's the right tool for the job, I am inclined to trust him on that barring further evidence that it is not...
Since when does Crockford say that JSMin is the right tool for this particular job: translating JSON5 into regular JSON?