This issue was originally put in on VS Code but was notified that this is a Prettier issue, reference: https://github.com/Microsoft/vscode/issues/29701
I have format on save set and when I go to try to save changes to my settings.json file I get this error (in title)
Screenshots below:

I can only confirm this is happening when saving settings.json (but it may be any .json file)
Yes, this is due to the token at (1:1) /
Comments are not part of the JSON spec 馃槩
Remove the top comment (and any other comment) to fix it.
Yes this definitely works but is this error something new that was added to Prettier because I've never seen it before, well since last week sometime.
This is a week old. Since prettier formats JSON(real json for now) and others: https://github.com/esbenp/prettier-vscode/releases/tag/v0.20.0
@CiGit thanks for clearing up my confusion!
I'm also getting this problem. What to do?
Remove anything that doesn't conform to the JSON spec, eg. comments (that's probably what is causing the issue, at least that was what was causing mine)
Is there a way to turn off parsing for particular files or allow non-strict JSON parsing?
For particular files, not yet.
non-strict JSON: not yet.
If you need to format pseudo JSON, IMO the best choice you have is to rely on the default formatter which does it's job.
To do so: empty jsonEnable array.
Related upstream issue https://github.com/prettier/prettier/issues/2378
Is it still not possible to have prettier ignore formatting settings.json file?
This issue is really annoying and I can't remove the comments from settings as I use them for my personal documentation.
@nikitavoloboev I believe it will be possible with the next prettier release since the fix was committed 7 days ago. No idea when it'll be out though.
"prettier.jsonEnable":[]
works for me.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Most helpful comment
Yes, this is due to the token at (1:1)
/Comments are not part of the JSON spec 馃槩
Remove the top comment (and any other comment) to fix it.