Initial public release of Warp.

Repo-Sync-Origin: warpdotdev/warp-internal@12af1d983b
This commit is contained in:
David Stern
2026-04-28 08:43:33 -05:00
commit 0dbd3d567a
4982 changed files with 1431549 additions and 0 deletions
+51
View File
@@ -0,0 +1,51 @@
#[cfg(not(target_arch = "wasm32"))]
use command::r#async::Command;
/// A wrapper around `path_env_var` that produces correctly-configured commands.
///
/// This follows the same wrapping pattern as `command::r#async::Command`:
/// callers construct commands through the executor, which transparently sets
/// the PATH environment variable. On wasm, a dummy implementation is provided
/// so that consumer code doesn't need cfg gating.
#[derive(Clone)]
pub struct CommandBuilder {
path_env_var: Option<String>,
}
impl CommandBuilder {
/// Creates a new CommandBuilder with the given PATH environment variable.
pub fn new(path_env_var: Option<String>) -> Self {
Self { path_env_var }
}
/// Returns the PATH environment variable, if set.
pub fn path_env_var(&self) -> Option<&str> {
self.path_env_var.as_deref()
}
/// Creates a new Command with PATH already set.
///
/// Use this when you need to run a command. The returned Command has the
/// same API as `command::r#async::Command`, so callers don't need to change
/// how they construct commands.
///
/// On Windows, the command is wrapped in `cmd.exe /c` so that `.cmd` and
/// `.bat` scripts on PATH are resolved correctly (e.g. `npm.cmd`,
/// `typescript-language-server.cmd`). Rust's `Command::new` uses
/// `CreateProcessW` which only resolves `.exe` extensions.
#[cfg(not(target_arch = "wasm32"))]
pub fn command(&self, program: impl AsRef<std::ffi::OsStr>) -> Command {
#[cfg(windows)]
let mut cmd = {
let mut cmd = Command::new("cmd.exe");
cmd.arg("/c").arg(program);
cmd
};
#[cfg(not(windows))]
let mut cmd = Command::new(program);
if let Some(path) = &self.path_env_var {
cmd.env("PATH", path);
}
cmd
}
}