taze mit Homebrew, Nix installieren

Projektlinks

• Homepage

Befehle und Aliase

• taze

Projektgeschichte

The repository was created in 2020 and the README identifies taze as a modern CLI tool for keeping dependencies fresh. It explains the name as Persian for fresh and credits Anthony Fu in the MIT license notice.

The README places taze in the same problem space as npm-check-updates and npm-check, while emphasizing a different balance: monorepo support, npx usage without installation, and safe-by-default updates inside allowed version ranges.

Adoptionsgeschichte

By 2026 the official GitHub repository metadata showed several thousand stars and more than one hundred forks, and the input metadata listed Homebrew and Nix packages. Its adoption is strongest among JavaScript and TypeScript users who want a small CLI rather than a hosted dependency bot.

Wie es verwendet wird

The common path is to run npx taze, optionally use -r for recursive monorepo scanning, and choose modes such as major, minor, patch, or stable to control how far versions are bumped. A taze.config.js file can store the same options available on the command line.

Warum Paket-Nerds sich dafür interessieren

taze matters to package-manager culture because it is a package about packages: it automates dependency freshness while still respecting semver ranges and lockfile-era caution. It is especially interesting for monorepo maintainers who want a local, scriptable alternative to bot-driven upgrade workflows.

Zeitleiste

• 2020: GitHub repository created.
• 2022: Public GitHub release history includes the 0.8 series.
• 2026: GitHub release metadata lists the 19.x series.

Related projects

• The README lists npm-check-updates and npm-check as inspirations or alternatives.

Quellen

• https://api.github.com/repos/antfu-collective/taze
• https://api.github.com/repos/antfu-collective/taze/releases
• https://github.com/antfu-collective/taze#readme
• input.source_facts.package-manager