Consider supporting importing files as jsonc / json5

[lucacasonato]

import data from "./data.jsonc" with { type: "jsonc" };
import data from "./data.json5" with { type: "json5" };

I'm not to sure about this myself yet, but it may be interesting. What are peoples' thoughts?

[lino-levan]

Although it may seem like a practical inclusion, I worry that it's straying away from web spec. How would we decide which formats to allow? Would tomls be importable? How about yaml? I don't see a clear way we can draw the line here. I'm open to hearing what you think, I'm just a little skeptical about Deno straying away from spec text.

[Jabolol]

Even though I agree with @lino-levan, since Deno supports deno.jsonc configuration files implementing this would make sense. There are times when one wants to store extra configuration in the deno.jsonc file to reference it in the project programmatically, and this would help.

[lino-levan]

Outside of static analysis, this doesn't provide a lot of benefit imo. Are there enough people asking for jsonc specifically? I'd love to get a sense of if people actually want this.

[scarf005]

i'd like to share my use-use:

• import fmt property of deno.jsonc
• feed it as an option to wasm dprint formatter
• use it for formatting texts programmatically

it's more of an workaround, however once deno exposes fmt as an runtime API (#10731).

[lino-levan]

Perhaps #19322 would be a less hacky way of doing it while not exposing a runtime API?

[pubmikeb]

JSON is a great (de-)serialization format for apps' configs and data.
However, it doesn't support comments. Luckly, there are two formats, which support comments in JSON: .jsonc and .json5.

As a modern application environment, it would be great to be able to use .jsonc and .json5 instead of classical .json in projects.

Following #20833, please add support importing files as .jsonc.

[Malix-Labs]

Also note that JSON5 is arguably a better spec than JSONC, see microsoft/vscode#100688