aef25a3bc3
This PR improves the setup instructions for the slash-commands-example extension by: 1. Replacing the `sed` command with a more reliable approach that completely replaces the Cargo.toml file. 2. Explicitly showing how to create a standalone extension with a properly configured Cargo.toml file that: - Uses `edition = "2021"` instead of `edition.workspace = true` - Doesn't include `publish.workspace = true` - Doesn't include the `[lints]` section This change addresses an issue where the extension wouldn't work when copied as a standalone project due to workspace references that are only valid when the extension is built as part of the main Zed repository. The updated instructions provide a clear, reliable path for developers to create their own Zed extensions based on the slash commands example. Release Notes: - N/A |
||
|---|---|---|
| .. | ||
| emmet | ||
| erlang | ||
| glsl | ||
| haskell | ||
| html | ||
| lua | ||
| perplexity | ||
| proto | ||
| purescript | ||
| ruff | ||
| slash-commands-example | ||
| snippets | ||
| terraform | ||
| test-extension | ||
| toml | ||
| uiua | ||
| zig | ||
| .gitignore | ||
| EXTRACTION.md | ||
| README.md | ||
Zed Extensions
This directory contains extensions for Zed that are largely maintained by the Zed team. They currently live in the Zed repository for ease of maintenance.
If you are looking for the Zed extension registry, see the zed-industries/extensions repo.
Structure
Currently, Zed includes support for a number of languages without requiring installing an extension. Those languages can be found under crates/languages/src.
Support for all other languages is done via extensions. This directory (extensions/) contains a number of officially maintained extensions. These extensions use the same zed_extension_api available to all Zed Extensions for providing language servers, tree-sitter grammars and tree-sitter queries.
Dev Extensions
See the docs for Developing an Extension Locally for how to work with one of these extensions.
Updating
Note
This update process is usually handled by Zed staff. Community contributors should just submit a PR (step 1) and we'll take it from there.
The process for updating an extension in this directory has three parts.
-
Create a PR with your changes. (Merge it)
-
Bump the extension version in:
- extensions/{language_name}/extension.toml
- extensions/{language_name}/Cargo.toml
- Cargo.lock
You can do this manually, or with a script:
# Output the current version for a given language ./script/language-extension-version <langname> # Update the version in `extension.toml` and `Cargo.toml` and trigger a `cargo check` ./script/language-extension-version <langname> <new_version>Commit your changes to a branch, push a PR and merge it.
-
Open a PR to
zed-industries/extensionsrepo that updates the extension in question
Edit extensions.toml in the extensions repo to reflect the new version you set above and update the submodule latest Zed commit.
# Go into your clone of the extensions repo
cd ../extensions
# Update
git checkout main
git pull
just init-submodule extensions/zed
# Update the Zed submodule
cd extensions/zed
git checkout main
git pull
cd -
git add extensions.toml extensions/zed