Repository navigation
Support editor setting for Zed #826
Description
Description
Zed is probably now the most popular code editor after VSCode。
Suggested solution
.zed/settings.json
Alternative
No response
Additional context
No response
Validations
- Read the Contributing Guidelines.
- Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- Check that there isn't already an issue requesting the same feature.
Activity
[-]Support editor setting for **zed** (`.zed/`)[/-][+]Support editor setting for **zed** (`.zed/`)[/+][-]Support editor setting for **zed** (`.zed/`)[/-][+]Support editor setting for Zed[/+]feat(cli): add Zed editor support for project creation (#832)
shinebayar-g commentedon Mar 27, 2026
Can we re-open this since
vite.config.tssettings andvite-plusdependency still doesn't work in Zed.alexanderzinolidis commentedon Apr 1, 2026
@shinebayar-g For me everything is working if I change
"configPath": "./.oxlintrc.json"to"configPath": "./vite.config.ts"insettings.jsonshinebayar-g commentedon Apr 1, 2026
@alexanderzinolidis
oxc-zedv0.4.5 was released yesterday which includes oxc-project/oxc-zed#141 which should have fixed this issue. I haven't had a time to check it yet, but you're probably using the new version.Update:
vite-plusis now working with the oxc-zed extension.silvenon commentedon Apr 11, 2026
Indeed, v0.4.6 fixed it! Initially it wasn't working for me so I thought it was still broken, but running
vp lintrevealed that the Vite Plus was failing to resolvevite.config.tsitself because for some reason I have to specify extensions for local modules.I'd prefer Oxc LSP to fail if the specified
configFilefailed to resolve, so that I know when it stopped working, but I assume this is a fallback feature.patspam commentedon Apr 20, 2026
Would be nice if the instructions said that you need to install the
oxc-zedextension to get it to work properlynaokihaba commentedon Apr 22, 2026
@fengmk2
The underlying technical issue has already been resolved in oxc-zed v0.4.6, and vp create/vp migrate now automatically generates .zed/settings.json as of #832. What's still missing is documentation on the IDE Integration page covering the Zed setup — including installing the oxc-zed extension and the manual config using configPath: "./vite.config.ts". I'd like to open a PR for that.
shinebayar-g commentedon Apr 22, 2026
@naokihaba fyi #832 generates different config than the example mentioned in the zed oxc extension repository https://github.com/oxc-project/oxc-zed/blob/main/examples/both/.zed/settings.json
not sure which one is correct. For example setting
configPath: nullas shown in the example vsconfigPath: './vite.config.ts'made no difference. It would be nice if the examples and docs were consistent in this regard.silvenon commentedon Apr 22, 2026
It's because
nullis probably the default value, meaning that it searches for default configs, starting with.oxlintrc.json,oxlint.config.ts, thenvite.config.ts(last one newly added).The example configs include a lot of extra stuff which is already true by default, like
run: 'onType'(I believe) for oxlint and'onSave'foroxfmt.Looking at the LSP documentation it's a bit unclear how exactly these configs are supposed to be, for example it documents
fmt.configFile, while I think underoxfmtit's enough to only sayconfigFile… to my knowledge there's no direct reference.shinebayar-g commentedon Apr 22, 2026
Yes that's another confusing one.
naokihaba commentedon Apr 23, 2026
@shinebayar-g @silvenon
Thanks for looking into this!
You're right — there are differences between what #832 generates and the oxc-zed example config.
That said, the example simply makes the default values explicit (e.g.
configPath: null),https://github.com/oxc-project/oxc/tree/main/crates/oxc_language_server
so I don't think this is a critical mismatch. If it turns out to be confusing,
it might be worth discussing over on the oxc-zed repository or in oxc_language_server.
The goal of this issue is to make sure Zed users can get started with Vite+ without confusion.
Auto-generation is already covered by #832, and the remaining task is documentation.
I'd like to keep this issue focused on Zed support and avoid letting the scope grow too wide.
fengmk2 commentedon Apr 23, 2026
@naokihaba By the way, here's a future idea: once we have the oxlint plugin #1408, we can use it to automatically fix these misconfiguration issues.
naokihaba commentedon Apr 23, 2026
That's a great idea! An oxlint plugin that validates the Zed config would be a nice
addition down the line.
naokihaba commentedon Apr 23, 2026
I've opened #1456 to capture the idea.
docs: add Zed integration details to IDE documentation (#1455)