Feat: use JSON5 instead of JSON.parse for friendly JSON syntax

json5

{
  // comments
  unquoted: 'and you can quote me on that',
  singleQuotes: 'I can use "double quotes" here',
  lineBreaks: "Look, Mom! \
No \\n's!",
  hexadecimal: 0xdecaf,
  leadingDecimalPoint: .8675309, andTrailing: 8675309.,
  positiveSign: +1,
  trailingComma: 'in objects', andIn: ['arrays',],
  "backwardsCompatible": "with JSON",
}

[davidtheclark]

I was not planning on using require for JSON files. I don’t think there’s a need.

I am not interested in going down a rabbit hole to support “other flavors of json”. The request to parse multiple flavors of JS opens the door to more than enough flexibility, I think. And YAML provides opportunity for comments outside of JS files.

If there’s some strong argument about why JSON5 is a superior config format in common situations, not just an arbitrary personal preference, I’d consider reopening this issue.

[olsonpm]

i think there’s work toward using require instead of parsing the file as a string. We’ll then allow consumers to pass their own require function. This is mainly to support es modules but your use-case will be covered here as well.

Anyway we can leave this issue open till that’s finished