# 使用 Homebrew, scoop 安装 ibazel

查看 ibazel 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

## 安装

```sh
sudo av install brew:ibazel
```

其他安装命令:

### macOS

- Homebrew (100%):

```sh
brew install ibazel
```

  证据: local Homebrew formula metadata

### Windows

- Scoop (92%):

```sh
scoop install extras/ibazel
```

  证据: Scoop official bucket manifest trees: bucket/ibazel.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1

## 软件包事实

- **软件包键:** brew:ibazel
- **软件包管理器:** Homebrew
- **版本:** 0.32.0
- **来源摘要:** Tools for building Bazel targets when source files change
- **主页:** <https://github.com/bazelbuild/bazel-watcher>
- **仓库:** <https://github.com/bazelbuild/bazel-watcher>
- **最后更新:** 2026-07-26T04:07:47+02:00
- **已生成:** 2026-08-03T19:37:03+00:00

## 可执行文件

- ibazel (别名)

## 安装行为

- Bottle: 不可用

## 版本和新鲜度

- 页面生成时间: 2026-08-03
- 管理器版本: 0.32.0
## 项目历史与用法

ibazel is the executable from Bazel watcher, a source-file watcher for Bazel projects that reruns `build`, `test`, or `run` targets after source changes.

### 项目历史

The Bazel watcher README frames the tool around a familiar edit-save-rerun loop: save a file, have tests rebuild, or restart a server after source changes. The repository states that it is not an official Google product, while it lives under the `bazelbuild` GitHub organization and uses Bazel itself for builds.

### 采用历史

ibazel became a common companion tool in Bazel-heavy developer workflows because it supplies the watch mode that many language-specific toolchains provide by default. Its README documents Homebrew, npm, Arch Linux AUR, and source-build installation paths, and Homebrew analytics show materially higher use than most packages in this batch.

### 使用方式

Developers run commands such as `ibazel build //path/to:target`, `ibazel test`, or `ibazel run` during active development. The output runner feature reads `%WORKSPACE%/.bazel_fix_commands.json` and can prompt for generated repair commands such as Buildozer or Gazelle invocations.

### 为什么软件包爱好者会关心

ibazel is package-nerd candy because it sits at the boundary of build systems, file watching, editor feedback, live reload, npm distribution, Homebrew bottles, and Bazel's own repository culture. It is small enough to be a CLI utility, but important enough to show how a build ecosystem fills ergonomic gaps around a deliberately explicit core build tool.

### 时间线

- v0.0.1: The repository contains an early public release tag.
- 2017: The README's profiler example records iBazel and Bazel version data around a development-server reload workflow.
- v0.15.x-v0.29.x: The tag history shows a long 0.x release series across the Bazel watcher repository.
- 2026: The GitHub releases page lists v0.29.0 as an April 2026 release.

### Related projects

- The README connects ibazel directly to Bazel and mentions generated repair workflows involving Buildozer and Gazelle. Its npm package path, `@bazel/ibazel`, also ties it into JavaScript projects using Bazel.

### 来源

- <https://formulae.brew.sh/formula/ibazel>
- <https://github.com/bazelbuild/bazel-watcher>
- <https://github.com/bazelbuild/bazel-watcher/releases>


## 安全说明

narrow executable package without higher-risk signals.

- **Geiger 风险:** 绿色 / 低
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: %WORKSPACE%/.bazel_fix_commands.json
- Windows: %WORKSPACE%/.bazel_fix_commands.json
## 其他软件包管理器记录

- Scoop - extras/ibazel: normalized package name match | Scoop official bucket manifest trees: bucket/ibazel.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/ibazel.yml](https://github.com/mxcl/pkgdb/blob/main/combined/ibazel.yml)


## 来源

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph