JSON

1# Bundled JSON server: `vscode-json-languageserver`, the same one VS Code's own2# JSON support is built on. Installed by `pnpm lsp:install`. See LSP-SERVERS.md.3#4# Schemas are deliberately not listed here. The server has no catalog logic of5# its own (VS Code feeds it the associations), so Tori fetches SchemaStore's6# catalog, caches it, and sends the result as `json/schemaAssociations`. That is7# what `schema_associations` below asks for.89schema_version = 110id = "json"11label = "JSON"12description = "JSON and JSONC with SchemaStore schemas, through the VS Code JSON server"13license = "Apache-2.0"14contributor = { name = "Tori", github = "gettori" }1516# `.git` alone, and `package.json` deliberately absent. `root_for` returns the17# first ancestor holding *any* marker, so a monorepo with a `package.json` in18# every package would get a server per package - and unlike tsserver, this one19# has no per-package configuration to be right about, so those sessions would20# differ in nothing but their cost. One session for the repo is both correct21# and much cheaper.22root_markers = [".git"]2324verified_against = "vscode-json-languageserver 1.3.4"25verified_on = "2026-08-05"2627# Send this server the SchemaStore catalog after initialize. Nothing else needs28# configuring: the notification handler applies the associations itself.29schema_associations = true3031# Reads documents and fetches schemas but executes nothing from the project, so32# it keeps working in a project the user has not trusted.33runs_project_code = false3435[languages]36json = "json"37jsonc = "jsonc"3839[launch]40kind = "bundled_node"41entry = "resources/lsp/node_modules/vscode-json-languageserver/bin/vscode-json-languageserver"42args = ["--stdio"]