Microsoft/vscode

Support naming settings.json as settings.jsonc (and others)

Open

#269824 opened on Oct 4, 2025

View on GitHub
 (13 comments) (5 reactions) (1 assignee)TypeScript (74,848 stars) (10,221 forks)batch import
feature-requesthelp wantedsettings-editor

Description

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.104.2
  • OS Version: Linux

Steps to Reproduce:

  1. Create .vscode/settings.json, .vscode/extensions.json, etc.
  2. Put a comment into that "JSON", as allowed by https://jsonc.org, used implicitly by VSC
  3. Use any other of about a billion existing tool which assumes that *.json are https://www.json.org and not https://jsonc.org
  4. See that tool fail, e.g. https://github.com/pre-commit/pre-commit-hooks/issues/1196

This was already reported in https://github.com/microsoft/vscode/issues/79744 over 6+ years ago.

Would a PR to add support for this be welcome?

Contributor guide