Package Manager Distributions
Relevant source files
The following files were used as context for generating this wiki page:
vscli is distributed across multiple package managers to ensure cross-platform availability and ease of installation for developers on Linux, macOS, and Windows. The project leverages standard ecosystem-specific repositories to provide pre-compiled binaries or source-based installations, ensuring the tool is accessible via common command-line interfaces.
The primary distribution channel is the Rust-native registry, but the project also maintains presence in system-level managers like Homebrew for Unix-like systems, and Chocolatey or Winget for Windows environments.
Sources: README.md:38-74, Cargo.toml:1-15
Supported Platforms and Managers
The following table summarizes the official distribution channels available for vscli:
| Package Manager | Platform | Installation Command |
|---|---|---|
| Cargo | Windows, Linux, macOS | cargo install vscli |
| Homebrew | Linux, macOS | brew install michidk/tools/vscli |
| Chocolatey | Windows | choco install vscli |
| Winget | Windows | winget install vscli |
Sources: README.md:42-74
Distribution Architecture
The distribution process is integrated into the project's metadata and continuous integration. While the source code is hosted on GitHub, the availability on various managers is facilitated by metadata defined in the project configuration.
Project Metadata
The Cargo.toml file serves as the source of truth for distribution metadata, including versioning, authorship, and licensing, which is consumed by the Crates.io registry and other downstream packagers.
[package]
name = "vscli"
version = "1.3.0"
edition = "2024"
authors = ["Michael Lohr <michael@lohr.dev>"]
license = "MIT"
repository = "https://github.com/michidk/vscli%22
Sources: Cargo.toml:1-11
Update Management
To maintain dependency health across these distributions, the project utilizes Renovate. This ensures that the underlying library dependencies (which eventually get compiled into the distributed binaries) stay up to date, particularly for security and performance.
{
"matchManagers": ["cargo"],
"groupName": "All Cargo Dependencies"
}
Sources: renovate.json:15-20
Installation Workflow
The following diagram illustrates how a user interacts with different package manager distributions to retrieve and execute vscli.
The diagram shows the path from the user's platform choice to the final executable binary. Sources: README.md:38-74, src/main.rs:25-30
Configuration and Subcommands
Once installed via any distribution channel, the vscli binary provides a unified interface across all platforms. The installation adds the vscli command to the system path, supporting two primary operational modes: open and recent.
CLI Interface Logic
The tool uses the clap crate to handle command-line arguments consistently regardless of the installation source.
| Subcommand | Alias | Description |
|---|---|---|
open | o | Opens a specific path in a dev container or editor. |
recent | ui | Opens an interactive TUI for recently used workspaces. |
Sources: src/opts.rs:48-77, src/main.rs:46-103
Dependency Management
The distributions rely on a specific Rust toolchain defined in the repository, ensuring that builds from source (like via cargo install) use the stable channel.
[toolchain]
channel = "stable"
components = [ "rustfmt", "clippy" ]
Sources: rust_toolchain.toml:1-3
Summary
vscli is broadly distributed to accommodate diverse development environments. By supporting Cargo, Homebrew, Chocolatey, and Winget, the project ensures that users can integrate the tool into their existing workflows with minimal friction. Maintenance of these distributions is supported by automated dependency updates and centralized project metadata in Cargo.toml.