zed
zed copied to clipboard
zed-industries
vscode extension support
Check for existing issues
- [X] Completed
Describe the feature
Hello Zed team,
As a user of Zed, I have been impressed with its speed and user-friendly interface. However, I believe that to attract more users to your platform, it would be beneficial to consider supporting VS Code extensions.
Many developers rely on VS Code extensions to enhance their workflow. The ability to leverage the vast library of VS Code extensions could make Zed more appealing to a wider audience. This could help improve the adoption of Zed. Moreover, I don't think many developers would want to rewrite their extensions for a small and new app like Zed, at least not just yet.
You can implement your custom extension API for more performance too, but it can come later. VS Code extension support is a must right out of the box imo.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
Is it even possible?
It is, but the amount of work here is pretty non-trivial:
- expose editor bindings for all the things that exist in vscode
- bridge/thunk things that work differently
- support a JS runtime environment for plugins
- support compatible plugin configuration storage
+1 with a suggestion If you manage to add vscode extensions support with a better way of handling the really heavy extensions (like eslint for example), I think a lot of people would be excited to try and maybe switch from vscode to zed
So far, vscode is very fast and solid overall, with that problem above as a small nuisance - not sure if the host editor (vscode/zed) can control and improve the behaviour of extensions or not though tbh
I would love to see this. I am sure it isn't trivial to implement, but the competitive adv. and stickiness of VS Code's extension ecosystem isn't trivial either.
I think it would not make sense to support every vscode extension out there.. only a specific subset
can we at least short list some?
I think you need a specification on which parts of the VSCode Extension API to support as a start .. And a way of telling if a specific extension does meet the supported criteria. Not an easy task I might say.
Likewise, I don't think Zed has a shot of being a daily driver for a large part of the market until extensions are supported. I had finally switched from pure vim to vscode after many years only because there were certain AI extensions that made my workflow far superior. And I think zed would need those too.
