Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Find a file
2023-04-22 05:53:48 +12:00
.github/workflows Use Node 18 on CI, for fetch API 2023-04-17 16:22:30 -07:00
.vscode
assets Add newline shortcuts for popular editors 2023-04-21 18:29:35 +03:00
crates Merge pull request #2402 from zed-industries/fix-panics 2023-04-22 05:53:48 +12:00
plugins Use the same serde version across the entire workspace 2023-03-28 09:42:00 -07:00
script Look for the main display always 2023-04-21 17:18:01 +03:00
styles Remove new CTA in copilot sign in UI 2023-04-19 16:39:55 -07:00
.dockerignore
.gitignore
.gitmodules
Cargo.lock Merge pull request #2402 from zed-industries/fix-panics 2023-04-22 05:53:48 +12:00
Cargo.toml Store buffer's diagnostic sets in a smallvec 2023-04-20 08:58:41 -07:00
Dockerfile
Procfile
README.md Add missing steps to the setup instructions 2023-03-03 11:36:26 -08:00

Zed

CI

Welcome to Zed, a lightning-fast, collaborative code editor that makes your dreams come true.

Development tips

Dependencies

  • Install Postgres.app and start it.

  • Install the LiveKit server and the foreman process supervisor:

    brew install livekit
    brew install foreman
    
  • Ensure the Zed.dev website is checked out in a sibling directory:

    cd ..
    git clone https://github.com/zed-industries/zed.dev
    
  • Initialize submodules

    git submodule update --init --recursive
    
  • Set up a local zed database and seed it with some initial users:

    Create a personal GitHub token to run script/bootstrap once successfully. Then delete that token.

    GITHUB_TOKEN=<$token> script/bootstrap
    

Testing against locally-running servers

Start the web and collab servers:

foreman start

If you want to run Zed pointed at the local servers, you can run:

script/zed-with-local-servers
# or...
script/zed-with-local-servers --release

Dump element JSON

If you trigger cmd-alt-i, Zed will copy a JSON representation of the current window contents to the clipboard. You can paste this in a tool like DJSON to navigate the state of on-screen elements in a structured way.

Licensing

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

  • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Wasm Plugins

Zed has a Wasm-based plugin runtime which it currently uses to embed plugins. To compile Zed, you'll need to have the wasm32-wasi toolchain installed on your system. To install this toolchain, run:

rustup target add wasm32-wasi

Plugins can be found in the plugins folder in the root. For more information about how plugins work, check the Plugin Guide in crates/plugin_runtime/README.md.