feat(vscode): sync formatter with supported files

[TheAlexLichter]

Syncs extensions and filenames with #16524. LSP support for it in #17655.

Resolves #16729

[Copilot]

Pull request overview

This PR synchronizes the VS Code formatter extension's supported file types with the upstream oxc repository changes from PR #16524. It expands formatter support to include JSON, JSONC, HTML, CSS, GraphQL, Handlebars, Markdown, and YAML files by adding their associated file extensions and special filenames.

Key Changes:

• Added support for multiple new file formats including JSON, JSONC, HTML, CSS, GraphQL, Handlebars, Markdown, and YAML
• Added 84 new file extensions to the supportedExtensions array
• Added 29 new special filenames to the specialFilenames array

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Sysix]

Could you test it with the language server?
I would expect this does work on the server side.

oxc/apps/oxfmt/src/lsp/server_formatter.rs

Line 253 in 2e8f469

let source_type = get_supported_source_type(&path).map(enable_jsx_source_type)?;

This line does not handle the json format.
And one extra request: start the extension when someone's open a json file:

oxc/editors/vscode/package.json

Lines 285 to 293 in 2e8f469

	"activationEvents": [
	"onLanguage:astro",
	"onLanguage:javascript",
	"onLanguage:javascriptreact",
	"onLanguage:svelte",
	"onLanguage:typescript",
	"onLanguage:typescriptreact",
	"onLanguage:vue"
	],

EDIT: is json handled by external formatter? When yes, this is not supported at the moment :/

[TheAlexLichter]

@Sysix yeah that was what I noticed when testing as well. In the linked PR, most new supported file types are handled by an external parser, not directly through oxfmt. Any chance the LSP could cover that as well?

Otherwise we have (another) CLI vs extension discrepancy

[Sysix]

@TheAlexLichter: @leaysgur wants to tackle this problem next week: https://discord.com/channels/1079625926024900739/1429522693190979685/1455525397792821299
Happy to help where I can :)

I am not sure if this can be done easily with the raw transfer, overlookmotel had some thoughts about calling it multiple times at the same time:
https://discord.com/channels/1079625926024900739/1080712072012238858/1443007033065340970

[TheAlexLichter]

Alright. moving to draft here for now until we got more on the LSP side. Thanks for the update 👍🏻

[leaysgur]

In addition to these, we can also format TOML. 😉

oxc/apps/oxfmt/src/core/support.rs

Lines 109 to 126 in c115f4e

	/// Returns `true` if this is a TOML file.
	fn is_toml_file(file_name: &str) -> bool {
	if TOML_FILENAMES.contains(file_name) {
	return true;
	}
	#[expect(clippy::case_sensitive_file_extension_comparisons)]
	if file_name.ends_with(".toml.example") || file_name.ends_with(".toml") {
	return true;
	}
	false
	}
	static TOML_FILENAMES: phf::Set<&'static str> = phf_set! {
	"Pipfile",
	"Cargo.toml.orig",
	};

[TheAlexLichter]

Added ✅

[Sysix]

Need someone to check my big comment :)