# Installer node-build avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de node-build pour les workflows d'agents IA.

## installation

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

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

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

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:node-build
- **Gestionnaire de paquets:** Homebrew
- **Version:** 5.4.47
- **Résumé source:** Install NodeJS versions
- **Page d'accueil:** <https://github.com/nodenv/node-build>
- **Dépôt:** <https://github.com/nodenv/node-build>
- **Dernière mise à jour:** 2026-07-30T03:55:33Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

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

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 5.4.47
## Historique du projet et usages

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.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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

### Sources

- <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>


## Notes de sécurité

Aucun manifest local de gestion des secrets correspondant n'a été trouvé pour node-build. Les métadonnées de paquet Nucleus restent publiées ici afin que la couverture future dispose d'une URL stable.



## 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)


## Sources

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