bun mit Homebrew, chocolatey, MacPorts, Nix, pacman, scoop, winget installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• bun
• bunx

Projektgeschichte

Bun was created as a response to the accumulated layers of Node.js-era JavaScript tooling. The official 1.0 announcement, published on September 8, 2023, framed Bun as a stable, production-ready toolkit for running, building, testing, and debugging JavaScript and TypeScript.

The project is powered by JavaScriptCore rather than V8 and is designed as a faster, leaner, more modern replacement for Node.js while preserving compatibility with npm packages, Node-style module resolution, CommonJS, ES modules, Web APIs, and many Node built-ins.

Bun's documentation later described it as written in Rust and powered by JavaScriptCore, while the GitHub README emphasizes that the single `bun` command includes the runtime plus test runner, script runner, package manager, and package runner.

Adoptionsgeschichte

Bun moved from an alternative runtime curiosity into mainstream JavaScript tooling after the 1.0 release because it promised speed without forcing developers to abandon existing package.json projects. Official install paths include shell installer, npm, Homebrew, Docker, and Windows PowerShell, and package-manager metadata now lists it across Homebrew, Chocolatey, MacPorts, Nix, pacman, Scoop, and winget.

Its adoption is tied to projects experimenting with faster local feedback loops: replacing Node for script execution, replacing npm/yarn/pnpm for installs, replacing Jest/Vitest in some tests, and replacing separate bundlers for simple build cases.

Wie es verwendet wird

Common commands include `bun run` for scripts and TypeScript files, `bun install` for npm-compatible dependency installation, `bun test` for tests, `bun build` for bundling, and `bunx` for executing packages. Configuration is optional and lives in local or global `bunfig.toml` files for Bun-specific settings.

Bun's package manager writes `node_modules`, reads package.json, uses a global cache, and supports workspaces and npm registry configuration. Because it aims to run existing Node.js applications with little or no change, usage often starts as a drop-in replacement for selected scripts rather than a full-stack rewrite.

Warum Paket-Nerds sich dafür interessieren

Bun is significant because it collapses several previously separate JavaScript package tools into one binary. For package historians, it marks a major post-Node/npm phase where runtime, package manager, test runner, and bundler compete as integrated developer platforms rather than independent commands.

It is also important because it made package-manager performance and lockfile workflows part of a runtime's identity. Bun's rise pressured the broader ecosystem to treat install speed, TypeScript startup, test speed, and Node compatibility as one developer-experience surface.

Zeitleiste

• 2023-09-08: Bun 1.0 announced as stable and production-ready.
• 2024: 1.x releases continued expanding Node.js compatibility and toolkit coverage.
• 2025: Official docs describe Bun as a runtime, package manager, test runner, and bundler for modern JavaScript and TypeScript apps.
• 2026-05: GitHub release feed shows Bun v1.3.14 with ongoing 1.3.x releases.

Related projects

• Bun is most directly related to Node.js, npm, yarn, pnpm, npx, ts-node, tsx, esbuild, webpack, Rollup, Parcel, Jest, Vitest, Deno, and the JavaScriptCore/WebKit project.

Quellen

• https://bun.com/blog/bun-v1.0
• https://bun.com/blog/bun-v1.0.md
• https://bun.com/docs
• https://bun.com/docs/index.md
• https://bun.com/docs/runtime/bunfig.md
• https://github.com/oven-sh/bun
• https://raw.githubusercontent.com/oven-sh/bun/main/README.md