1# Zed
2
3[](https://github.com/zed-industries/zed/actions/workflows/ci.yml)
4
5Welcome to Zed, a lightning-fast, collaborative code editor that makes your dreams come true.
6
7## Development tips
8
9### Dependencies
10
11* Install Xcode from https://apps.apple.com/us/app/xcode/id497799835?mt=12, and accept the license:
12 ```
13 sudo xcodebuild -license
14 ```
15
16* Install homebrew, node and rustup-init (rutup, rust, cargo, etc.)
17 ```
18 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
19 brew install node rustup-init
20 rustup-init # follow the installation steps
21 ```
22
23* Install postgres and configure the database
24 ```
25 brew install postgresql@15
26 brew services start postgresql@15
27 psql -c "CREATE ROLE postgres SUPERUSER LOGIN" postgres
28 psql -U postgres -c "CREATE DATABASE zed"
29 ```
30
31* Install the `LiveKit` server and the `foreman` process supervisor:
32
33 ```
34 brew install livekit
35 brew install foreman
36 ```
37
38* Ensure the Zed.dev website is checked out in a sibling directory and install it's dependencies:
39
40 ```
41 cd ..
42 git clone https://github.com/zed-industries/zed.dev
43 cd zed.dev && npm install
44 npm install -g vercel
45 ```
46
47* Return to Zed project directory and Initialize submodules
48
49 ```
50 cd zed
51 git submodule update --init --recursive
52 ```
53
54* Set up a local `zed` database and seed it with some initial users:
55
56 [Create a personal GitHub token](https://github.com/settings/tokens/new) to run `script/bootstrap` once successfully: the token needs to have an access to private repositories for the script to work (`repo` OAuth scope).
57 Then delete that token.
58
59 ```
60 GITHUB_TOKEN=<$token> script/bootstrap
61 ```
62
63* Now try running zed with collaboration disabled:
64 ```
65 cargo run
66 ```
67
68### Common errors
69
70* `xcrun: error: unable to find utility "metal", not a developer tool or in PATH`
71 * You need to install Xcode and then run: `xcode-select --switch /Applications/Xcode.app/Contents/Developer`
72 * (see https://github.com/gfx-rs/gfx/issues/2309)
73
74### Testing against locally-running servers
75
76Start the web and collab servers:
77
78```
79foreman start
80```
81
82If you want to run Zed pointed at the local servers, you can run:
83
84```
85script/zed-with-local-servers
86# or...
87script/zed-with-local-servers --release
88```
89
90### Dump element JSON
91
92If 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](https://chrome.google.com/webstore/detail/djson-json-viewer-formatt/chaeijjekipecdajnijdldjjipaegdjc?hl=en) to navigate the state of on-screen elements in a structured way.
93
94### Licensing
95
96We use [`cargo-about`](https://github.com/EmbarkStudios/cargo-about) to automatically comply with open source licenses. If CI is failing, check the following:
97
98- 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.
99- 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`.
100- 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](https://embarkstudios.github.io/cargo-about/cli/generate/config.html#crate-configuration).
101
102
103### Wasm Plugins
104
105Zed 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:
106
107```bash
108rustup target add wasm32-wasi
109```
110
111Plugins can be found in the `plugins` folder in the root. For more information about how plugins work, check the [Plugin Guide](./crates/plugin_runtime/README.md) in `crates/plugin_runtime/README.md`.