Use the Vite+ Zed settings

[kmcginnes]

Summary

Zed was formatting through an external command and had no lint server, while the docs already ask Zed users to install oxc-zed. This switches .zed/settings.json to the settings Vite+ generates for Zed, so format-on-save and inline lint come from the oxfmt and oxlint language servers, both reading vite.config.ts.

 {
-  "format_on_save": "on",
-  "formatter": [{ "external": { "command": "pnpm", "arguments": ["exec", "vp", "fmt", "--stdin-filepath", "{buffer_path}"] } }],
   "lsp": {
+    "oxlint": { "initialization_options": { "settings": { "run": "onType", "typeAware": true, ... } } },
+    "oxfmt": { "initialization_options": { "settings": { "fmt.configPath": "./vite.config.ts", "run": "onSave" } } },
     "tailwindcss-language-server": { ... }
   },
   "languages": {
+    // one entry per language Vite+ formats (17), each using the oxfmt language server
+    // JavaScript also runs source.fixAll.oxc
     "CSS": { "language_servers": ["tailwindcss-intellisense-css", "!vscode-css-language-server", "..."] }
   }
 }

The Tailwind lsp block and the CSS language_servers override are kept from the old file. The CSS list gains "..." so the oxfmt and oxlint servers still start for CSS; without it Zed runs only the servers listed by name.

Verified live: in Zed with oxc-zed, format on save and inline lint.

Merge Danger

Door: two-way

Impact: Zed users

Without the oxc-zed extension, Zed no longer formats on save. docs/development.md already tells Zed users to install it.

Related

• Related to Migrate the toolchain to Vite+ #2305