Install babel with Homebrew, dnf

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• babel
• babel-external-helpers

Project history

Babel began as 6to5, a tool focused on compiling ES6-era JavaScript down to ES5. In February 2015 the project announced its rename to Babel, arguing that its parser and transpiler infrastructure would remain useful beyond a single ES6-to-ES5 migration window.

The official documentation now describes Babel as a broader toolchain: it transforms syntax, supports missing features through third-party polyfills such as core-js, performs source-code transformations, supports JSX, Flow, and TypeScript syntax, and is built from composable plugins and presets.

Major releases mark Babel's evolving role in the JavaScript ecosystem: Babel 6 modularized the package family, Babel 7 became the long-lived default generation for modern JavaScript tooling, and the official blog announced Babel 8 in 2026 with ESM-only packaging, dropped ES5 defaults, and a migration path for current users.

Adoption history

Babel's adoption followed the rise of ES2015+, React JSX, and npm-based frontend build pipelines. Its own 2015 rename post noted that 6to5 and 6to5-core were approaching half a million downloads and expected to pass a million soon, already signaling rapid uptake before the Babel name had fully settled.

By 2021, the Babel project described itself as used by millions while discussing project funding. The package metadata in this batch is narrower because the Homebrew formula is only the CLI package, but the npm ecosystem around @babel/core, @babel/cli, presets, and plugins is the real adoption center.

How it is used

Developers use Babel through @babel/core, @babel/cli, bundler integrations, presets, and plugins. Typical use cases include compiling newer ECMAScript syntax, JSX, TypeScript or Flow syntax stripping, proposal syntax experiments, and custom codemods.

Configuration is project-local and can live in babel.config.* files, .babelrc variants, or a babel key in package.json. That configurability is part of why Babel works both as a command-line package and as a library embedded by larger build tools.

Why package nerds care

Babel is one of the defining JavaScript package-manager stories: a compiler decomposed into many small npm packages, presets, plugins, helpers, parser packages, and runtime packages that are assembled by user configuration.

For package nerds, Babel also demonstrates both the power and cost of ecosystem-scale toolchains. It made future JavaScript usable early, but it also made package graphs, peer dependencies, semver ranges, and build-step reproducibility central concerns for frontend projects.

Timeline

• 2015: 6to5 is renamed Babel on the official blog.
• 2015: Babel 5 and Babel 6 release posts appear in the official blog archive.
• 2018: Babel 7 is released, becoming the long-lived generation of the toolchain.
• 2021: Babel publishes a funding update describing the project as used by millions.
• 2026: Babel 8 is released with ESM-only packaging and changed defaults.

Related projects

• core-js is the polyfill project Babel documentation points to for missing runtime features.
• ESTree, Acorn, Esprima, ESLint, and related parser projects shaped the JavaScript syntax tooling environment Babel grew up in.
• React popularized JSX workflows that made Babel a default part of frontend builds.
• TypeScript and Flow are type-syntax ecosystems Babel can parse or strip without doing type checking.

Sources

• https://babeljs.io/blog/2015/02/15/not-born-to-die
• https://babeljs.io/blog/2018/08/27/7.0.0
• https://babeljs.io/blog/2021/05/10/funding-update
• https://babeljs.io/blog/2026/06/16/8.0.0
• https://babeljs.io/docs/
• https://babeljs.io/docs/config-files
• https://github.com/babel/babel