# node-build mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für node-build in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:node-build
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install node-build
```

  Evidenz: local Homebrew formula metadata

## Paketfakten

- **Paketschlüssel:** brew:node-build
- **Paketmanager:** Homebrew
- **Version:** 5.4.47
- **Quellzusammenfassung:** Install NodeJS versions
- **Homepage:** <https://github.com/nodenv/node-build>
- **Repository:** <https://github.com/nodenv/node-build>
- **Zuletzt aktualisiert:** 2026-07-30T03:55:33Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- node-build (Alias)
- nodenv-install (Alias)
- nodenv-uninstall (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 5.4.47
## Projektgeschichte und Nutzung

node-build is the small installer layer behind nodenv's `nodenv install` workflow. Its upstream README describes it as a tool that downloads, compiles, and installs Node on Unix-like systems, either as a nodenv plugin or as the standalone `node-build` command.

### Projektgeschichte

The project is explicitly descended from rbenv's ruby-build: the node-build README credits Sam Stephenson's ruby-build as the fork source and Will McKenzie as the person who modified it for Node. That lineage explains the package's shape: shell scripts, build definitions, optional source compilation, tarball checksums, mirrors, and environment-variable overrides instead of a large application framework.

### Adoptionsgeschichte

node-build is niche compared with Node itself, but it matters to developers who want repeatable per-project Node installs through nodenv. Homebrew Formulae lists node-build 5.4.44 and reports 28,881 installs over 365 days, including 13,982 installs on request, which is enough signal to treat it as a real version-manager dependency rather than a forgotten helper.

### Wie es verwendet wird

Package nerds use node-build when they want nodenv-style version management without nvm's shell-function model. Typical commands are `nodenv install --list`, `nodenv install 20.11.1`, `node-build --definitions`, and `node-build 20.11.1 ~/local/node-20.11.1`. The advanced knobs are useful when diagnosing C compiler failures, forcing source builds with `--compile`, applying a patch with `--patch`, keeping sources for debugging, or overriding tarball URLs and mirrors.

### Warum Paket-Nerds sich dafür interessieren

The package is interesting because it encodes the boring but valuable part of a runtime ecosystem: mapping many upstream Node releases into reproducible install recipes. It is not a general JavaScript tool; it is plumbing for people who care which exact Node binary, checksum, compiler, prefix, or mirror produced their local runtime.

### Related projects

- nodenv
- node-build-update-defs
- rbenv/ruby-build
- Node.js

### Quellen

- <https://formulae.brew.sh/formula/node-build>
- <https://github.com/nodenv/node-build>
- <https://github.com/nodenv/nodenv>
- <https://raw.githubusercontent.com/nodenv/node-build/main/README.md>
- <https://raw.githubusercontent.com/nodenv/node-build/main/package.json>


## Sicherheitshinweise

Für node-build wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.



## Combined YAML source

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


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph