# Installer gulp-cli avec Homebrew, chocolatey, apt, pacman Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de gulp-cli pour les workflows d'agents IA. ## installation ```sh sudo av install brew:gulp-cli ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install gulp-cli ``` Preuve: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install gulp ``` Preuve: Debian stable package indexes: gulp from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - pacman (92%): ```sh sudo pacman -S gulp ``` Preuve: Arch Linux sync databases: gulp from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - Chocolatey (92%): ```sh choco install gulp-cli ``` Preuve: Chocolatey community package catalog: gulp-cli from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='10.804','zoxide' ## Faits du paquet - **Clé du paquet:** brew:gulp-cli - **Gestionnaire de paquets:** Homebrew - **Version:** 3.1.0 - **Résumé source:** Command-line utility for Gulp - **Page d'accueil:** - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - gulp (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 3.1.0 ## Historique du projet et usages gulp-cli is the command-line launcher for gulp, the JavaScript build-system and task-runner ecosystem. Its package-manager role is deliberately split from the local gulp library: users install the CLI as a global or package-manager-provided command, while each project keeps its own gulp dependency and gulpfile. ### Historique du projet The gulp-cli repository was created in December 2014, and the npm package was first published as 0.1.0 later that month. That timing matches gulp's move away from a single globally installed gulp package toward a small command shim that locates and runs the gulp version installed in a project. The 1.0.0 npm publication in November 2015 stabilized the split CLI model. The 2.x line, published from December 2017, sat alongside gulp 4-era workflows, and the 3.0.0 changelog in March 2024 records modernization work such as Liftoff v5, removal of older flags, and support work for future gulp handlers. ### Historique d'adoption The official quick-start documentation teaches `npm install --global gulp-cli` before `npm install --save-dev gulp`, so gulp-cli became the package users and OS package maintainers expose as the executable named `gulp`. Homebrew, Chocolatey, Debian, Ubuntu, Arch, and other package indexes package the CLI separately or map it to the `gulp` command, reflecting its status as the distribution-friendly entry point rather than the project-local build library. ### Modes d'utilisation Users invoke `gulp [flags] ...` from a project tree. The CLI discovers the gulpfile, loads project-local gulp, prints task trees, supports completion, and accepts configuration through `.gulp.*` files in the current directory hierarchy or the home directory. For package users, the practical distinction matters: upgrading the command-line package changes the launcher, while task semantics are mainly controlled by the project's pinned gulp and plugin dependencies. ### Pourquoi les passionnés de paquets s'y intéressent gulp-cli is a clean example of the global-shim/local-library pattern in Node packaging. It reduces global dependency drift, lets different projects use different gulp versions, and gives package managers a small executable package that can be updated without rewriting every project's build stack. Its history is also a packaging lesson from the task-runner boom: the command name stayed stable, but ownership of behavior moved into the project dependency graph. ### Chronologie - 2014: GitHub repository created and npm package 0.1.0 published. - 2015: npm package 1.0.0 published. - 2017: v2.0.0 release published. - 2024: v3.0.0 changelog records CLI modernization and removal of older compatibility paths. - 2025: v3.1.0 changelog records support for top-level await on newer Node 22 builds. ### Related projects - gulp is the local task-runner library that gulp-cli launches. - Liftoff is the Node CLI bootstrap library used by gulp-cli. - Interpret is used by gulp-cli to support JavaScript-variant configuration and gulpfiles. ### Sources - - - - - ## Notes de sécurité narrow executable package without higher-risk signals. - **Risque Geiger:** vert / faible - 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: .gulp.*, ~/.gulp.* ## Autres enregistrements de gestionnaires de paquets - Chocolatey - gulp-cli: normalized package name match | Chocolatey community package catalog: gulp-cli from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='10.804','zoxide' - Debian apt - gulp - 4.0.2+~cs54.26.36-8: installed executable or alias match | Debian stable package indexes: gulp from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | streaming build system to automate painful or time-consuming tasks | https://gulpjs.com - Ubuntu apt - gulp - 4.0.2+~cs54.26.36-6: installed executable or alias match | Ubuntu 24.04 LTS package indexes: gulp from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | streaming build system to automate painful or time-consuming tasks | https://gulpjs.com - pacman - gulp - 5.0.1-1: installed executable or alias match | Arch Linux sync databases: gulp from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | The streaming build system | https://gulpjs.com/ ## Combined YAML source View the package source record on GitHub. [combined/gulp-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gulp-cli.yml) ## Sources - 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