Installer vale avec Homebrew, apk, chocolatey, MacPorts, Nix, pacman, zypper, scoop, winget

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• vale

Historique du projet

Vale's GitHub releases go back to v0.1.0 in February 2017. The modern repository describes Vale as a fast, cross-platform command-line tool for code-like linting of prose, and the official documentation clarifies that it is not a general-purpose grammar checker.

The project evolved from a CLI into a small ecosystem. The official docs list the main `vale` CLI repository, `vale-ls` as an LSP implementation for the CLI, and `vale.sh` as the website and documentation project.

Historique d'adoption

Vale's adoption has been strongest in documentation, developer-education, and technical-writing repositories where style-guide enforcement needs to run in local editors and CI. The docs list integrations for CircleCI, GitHub Actions, pre-commit, JetBrains IDEs, Obsidian, Oxygen XML, Sublime Text, Neovim, VS Code, Qt Creator, and Zed.

The input shows broad package-manager reach across Alpine, Homebrew, Chocolatey, MacPorts, Nix, Arch, Scoop, winget, and openSUSE. The official installation docs also point to GitHub release binaries, Docker images, and community-maintained package repositories.

Modes d'utilisation

A typical Vale setup has a `.vale.ini` file, a StylesPath directory, and documents to lint. The docs describe CLI commands such as `sync`, `ls-config`, `ls-dirs`, `--config`, `--glob`, `--output`, and exit codes suitable for CI failure.

Vale's package system lets projects share, extend, sync, and update configurations. Official docs describe packages as zip files or directories containing a `.vale.ini`, a StylesPath folder, or both, with official Package Explorer names, URLs, local zip files, and local directories accepted as package sources.

Vale's markup awareness is central to its use: the README says it understands many markup formats so it can avoid syntax-related false positives and exclude code snippets from prose rules. The docs describe supported markup formats such as Markdown, AsciiDoc, and reStructuredText.

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

Vale matters to package nerds because it turns prose quality checks into a normal CLI dependency. It is easy to pin in Homebrew, winget, Chocolatey, Docker, pre-commit, or CI, and it avoids forcing every documentation repository to install a language runtime just to lint text.

It also brings package-manager thinking to style guides themselves: packages, StylesPath, vocabularies, and synced external styles make editorial policy behave like versioned dependencies.

Chronologie

• 2017: v0.1.0 GitHub release is published.
• 2021: v2.10.3 appears in the older release page range.
• 2026: v3.13.0 adds tree-sitter support for Java source-code files.
• 2026: v3.14.0 adds Dasel v3 support.

Related projects

• vale-ls provides Language Server Protocol support for the Vale CLI.
• GitHub Actions, pre-commit, VS Code, Neovim, and other editor/CI integrations make Vale part of documentation workflows.
• External style packages such as Google, Microsoft, and write-good-style rules are part of the ecosystem Vale can enforce.

Sources

• https://api.github.com/repos/vale-cli/vale/releases?per_page=100&page=2
• https://docs.vale.sh/
• https://docs.vale.sh/keys/packages
• https://docs.vale.sh/topics/cli
• https://docs.vale.sh/topics/installation
• https://github.com/vale-cli/vale
• https://github.com/vale-cli/vale/releases
• source_facts.package-manager