Installation

Get Dependi up and running in your Zed Editor.

Table of contents

  1. From Zed Extensions (Recommended)
  2. Manual Installation (Development)
    1. Prerequisites
    2. Build Steps
  3. Verify Installation
  4. System Requirements
    1. Supported Platforms
    2. Network Requirements
  5. What’s Next?

The easiest way to install Dependi:

  1. Open Zed editor
  2. Press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Linux/Windows)
  3. Type “extensions” and select zed: extensions
  4. Search for “Dependi”
  5. Click Install

The extension automatically downloads and installs the language server for your platform.

Manual Installation (Development)

For development or testing pre-release versions:

Prerequisites

  • Rust 1.75+ (tested with 1.91.1)
  • wasm32-wasip1 target: rustup target add wasm32-wasip1

Build Steps

  1. Clone the repository: 
    git clone https://github.com/mpiton/zed-dependi.git
cd zed-dependi
  2. Build the LSP: 
    cd dependi-lsp
cargo build --release
  3. Build the extension: 
    cd ../dependi-zed
cargo build --release --target wasm32-wasip1
  4. Install as dev extension in Zed:
    • Open Zed
    • Run command: zed: install dev extension
    • Select the dependi-zed directory

Verify Installation

After installation, open any supported dependency file to verify Dependi is working:

  1. Open a Cargo.toml, package.json, or other dependency file
  2. You should see inlay hints next to your dependencies showing version status
  3. Hover over a dependency to see package information

If you don’t see hints:

  • Check if the extension is enabled in Zed’s extensions panel
  • View Zed logs for errors: run zed --foreground from terminal
  • See Troubleshooting for common issues

System Requirements

Supported Platforms

Platform Architecture Status
Linux x86_64 Supported
Linux aarch64 Supported
macOS x86_64 (Intel) Supported
macOS aarch64 (Apple Silicon) Supported
Windows x86_64 Supported

Network Requirements

Dependi needs network access to package registries and the vulnerability database:

Service URL Purpose
crates.io https://crates.io Rust packages (+ your alternative registry URLs)
npm https://registry.npmjs.org Node.js packages
PyPI https://pypi.org Python packages
Go Proxy https://proxy.golang.org Go modules
Packagist https://packagist.org PHP packages
pub.dev https://pub.dev Dart packages
NuGet https://api.nuget.org .NET packages
RubyGems https://rubygems.org Ruby gems
OSV.dev https://api.osv.dev Vulnerability data

If you’re behind a corporate firewall, ensure these URLs are allowed.

What’s Next?