4 ms·
It's 2023 and NPM still doesn't support a comma after the last item in a list, and no comments. It's still stuck to the same old JSON version that it used on da
by WirelessGigabit 3y ago
It's 2023 and NPM still doesn't support a comma after the last item in a list, and no comments. It's still stuck to the same old JSON version that it used on day one.
Also, I started with `grunt` before using `gulp`. And I used `bower_components` to build a website. I try not to remember too much though. There is only so much that therapy helps.
I just do Rust now. It's not perfect by any means but at least there is design there.
- troupo 3y ago> It's 2023 and NPM still doesn't support a comma after the last item in a list, and no comments. It's still stuck to the same old JSON version that it used on day one. Because that's the only version of JSON. It never changed: https://www.json.org/json-en.html https://www.json.org/json-en.html
- WirelessGigabit 3y agohttps://spec.json5.org/ https://spec.json5.org/ Maybe not by the original people, but still a superset. And a more useable superset.
- troupo 3y agoThere are multiple supersets of JSON with various degrees of adoption. Adopting anything else but JSON would probably break innumerable tools that rely on the package.json format. Note: the stable version of json5 spec was only released in 2018.
- pvillano 3y ago# Parsing JSON is a Minefield "The conciseness of the grammar leaves many aspects undefined. On top of that, several specifications exist, and their various interpretations tend to be murky." https://seriot.ch/projects/parsing_json.html https://seriot.ch/projects/parsing_json.html
- pvillano 3y agoIt gets worse: parser differences can create security risks "An Exploration of JSON Interoperability Vulnerabilities" https://bishopfox.com/blog/json-interoperability-vulnerabilities https://bishopfox.com/blog/json-interoperability-vulnerabili...