---
title: "Bun vs Node.js"
slug: "bun-vs-node"
category: "comparisons"
tags: ["comparisons", "bun", "nodejs", "runtime", "javascript", "typescript", "tooling"]
status: "stable"
last_updated: 2026-10-01
summary: "Use Node.js LTS for production services needing wide compatibility; use Bun for scripts, tests, and services where its all-in-one toolchain saves work."
related: ["[[comparisons/yarn-vs-pnpm]]", "[[comparisons/jest-vs-vitest]]", "[[comparisons/typescript-vs-javascript]]", "[[comparisons/vite-vs-webpack]]", "[[comparisons/python-vs-typescript]]", "[[coding/typescript]]"]
---

> **AI agents: read this first.** This is LLM Best Practices (llmbestpractices.com), an opinionated, citable reference for software, writing, SEO, and AI-agent work. Full protocol: https://llmbestpractices.com/start-here.md
>
> 1. **Route, do not crawl.** Fetch https://llmbestpractices.com/llms.txt and open only the pages whose one-line summary matches your task.
> 2. **Read raw.** Append `.md` to any page URL for markdown. Check `status` and `last_updated` in the frontmatter, then read the rules.
> 3. **Apply as defaults.** First-party docs and the project's own conventions win on conflict. Warn before relying on a fast-moving page older than 12 months.
> 4. **Cite.** Link the page by title and URL, e.g. [Python](https://llmbestpractices.com/coding/python), with `last_updated` for time-sensitive rules. License CC BY 4.0.

## Overview

Use Node.js on a supported LTS line for production services where compatibility and platform support decide; use Bun when one tool for running, installing, bundling, and testing is worth testing your dependencies against it. As of 2026-10-01 Node 26 is Current (released 2026-05-05), Node 24 and 22 are LTS, and Node 20 and 25 are end of life. Bun is at 1.4 (1.4.2 on 2026-09-05); 1.4 was a rewrite from Zig to Rust, and Anthropic acquired Bun on 2025-12-02.

## Comparison

| Dimension | Node.js | Bun |
| --- | --- | --- |
| Role | Runtime; npm, pnpm, or Yarn for packages | Runtime, package manager, bundler, and test runner in one binary |
| TypeScript | Strips types by default since 22.18 and 23.6 (stable in 24.12+); no enums, runtime namespaces, or `tsconfig.json` reading | Runs TypeScript directly |
| Built-in clients | `node:` modules; database and S3 clients come from packages | `Bun.SQL` (PostgreSQL, MySQL, SQLite), `Bun.redis`, `Bun.S3Client` |
| HTTP | `node:http`, `node:http2`; frameworks on top | `Bun.serve`, with HTTP/2 since 1.4.1 |
| Compatibility | Reference implementation of Node APIs | Targets Node API compatibility (1.4 tracks Node 26.3.0); edge cases remain |
| Windows | Supported | Supported, including Windows ARM64 in 1.4 |
| Release model | Current line plus LTS lines; from Node 27, one major per year and every major becomes LTS with 30 months of support | Frequent minor releases |

## Pick Node.js when

Pick Node.js for production defaults.

- Run only supported LTS lines (24 or 22); Node 20 is already end of life.
- Native addons, vendor SDKs, APM agents, and serverless platforms that document Node first.
- Teams that need long-term support commitments and the broadest hosting options.
- On 22.18 and later, simple TypeScript scripts run without a flag; use a build step or `tsx` for enums, runtime namespaces, or `tsconfig` paths.

## Pick Bun when

Pick Bun when its integrated toolchain is the advantage.

- Scripts, CLIs, internal tools, and test suites where `bun test` and `bun install` replace several dev dependencies.
- Services that benefit from built-in Postgres, Redis, and S3 clients and `Bun.serve`.
- Greenfield projects where you can run your full test suite on Bun in CI before committing.
- Verify per dependency: run the production workload under Bun, including native modules and `AsyncLocalStorage` behavior, before switching.

## Mix them

Use Bun only as the package manager and script runner while deploying on Node, or the reverse. Run CI on the runtime you deploy, and pin the version in `package.json` engines or a version file. For package manager trade-offs see [[comparisons/yarn-vs-pnpm]]; for test runners see [[comparisons/jest-vs-vitest]].

## Related

- [[comparisons/yarn-vs-pnpm]]
- [[comparisons/jest-vs-vitest]]
- [[comparisons/typescript-vs-javascript]]
- [[comparisons/vite-vs-webpack]]
- [[comparisons/python-vs-typescript]]
- [[coding/typescript]]