Still running Babel?

Babel preset-env or plugin order fighting you? We fix it.

Babel remains the quiet workhorse underneath a lot of production JavaScript, especially on long-lived codebases that never migrated away. The pain is almost always in the preset-env targets, a plugin order that was correct once and is subtly wrong now, or decorator and class field semantics drifting between stages. We bring the config back to something you can read, upgrade and keep.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

babel.log

still broken

What it is

Babel at a glance

Babel is a JavaScript transpiler that turns modern syntax into code older environments can run. It started in 2014 as 6to5, created by Sebastian McKenzie, was renamed Babel in 2015, and has shipped majors every few years since. It is open source under the MIT license and maintained by a collective of volunteers and company engineers.

The tool is organized around presets and plugins. @babel/preset-env targets a browserslist query and includes just the transforms needed for that set. @babel/preset-react, @babel/preset-typescript and @babel/preset-flow handle JSX, TypeScript stripping and Flow stripping. A long tail of plugins covers class fields, decorators, private methods, pipeline operator proposals, and most legacy syntax people still need.

Type
JavaScript and TypeScript transpiler
First released
2014 as 6to5, 2015 as Babel
License
MIT, open source
Maintained by
The Babel team and contributors
Typically used for
Compiling modern syntax for older browsers, JSX transforms, TypeScript stripping, decorator and class-field handling

The honest version

Babel pros and cons

No technology is all upside. This is where Babel earns its place and where it tends to cause trouble.

Where Babel is strong

  • Ecosystem ubiquityIf your project is older than a couple of years, Babel is almost certainly in it. Every major framework and bundler has a Babel integration path, and most engineers have used it at some point.
  • preset-env tracks browsers for youA single browserslist query drives which transforms are included. The pipeline shrinks as your audience modernizes, with no manual plugin trimming required.
  • Powerful plugin and AST APICustom code transforms, compile-time instrumentation, and bespoke syntax extensions are all reachable through a stable visitor API that has survived many majors.
  • TypeScript stripping is quick@babel/preset-typescript removes types without running the type checker, which keeps the build fast and leaves type checking to tsc as a separate step.
  • JSX and framework supportReact, Preact, Vue, Solid and others ship Babel plugins or depend on them indirectly. Framework upgrades usually come with a drop-in plugin change rather than a rewrite.
  • Mature and predictableAfter a decade of production use, the sharp edges are documented, the fixes are known, and the output is stable enough that bytecode diffs between releases are reviewable.

Where Babel bites

  • Slow compared to Rust and Go toolchainsesbuild, SWC and OXC are all between 10x and 100x faster. On a large codebase the Babel step is now the obvious bottleneck in a modern build graph.
  • preset-env targets are easy to get wrongA 'last 2 versions' query includes Safari 16, which still needs some transforms. Most teams either over-transpile and ship more code than needed, or under-transpile and break on a real device.
  • Plugin order silently mattersA decorators plugin running after class properties produces a subtly different output. There is no warning; the test suite passes and a bug hits production six weeks later.
  • Decorators and class fields churned for yearsLegacy decorators, stage-2, stage-3 and now TC39 decorators all live in the Babel repo, and projects that upgraded gradually have config comments explaining which stage they picked.
  • Deprecated plugin names linger@babel/plugin-proposal-* were renamed to @babel/plugin-transform-*. Old configs still reference the proposal names and get noisy warnings on every build.
  • Hiring interest has moved onCandidates are more likely to have shipped Vite or Turbopack projects in the last two years than to have maintained a Babel config. The skill is still around; it is less common than it was.

Sound familiar?

Common Babel problems we fix

The Babel problems that bring people to us, and what you have once each one is fixed.

Support for the experimental syntax 'decorators'

Decorators refuse to parse

A codebase using decorators without @babel/plugin-proposal-decorators (or the newer transform plugin), or a mismatch between the chosen stage and what the runtime expects.

Decorators parsing on the stage you chose

regeneratorRuntime is not defined

Async transforms break at runtime

preset-env transpiling async functions down for older targets without the matching regenerator runtime, usually because core-js and @babel/runtime were never installed or were pinned to incompatible versions.

Async functions running everywhere

@babel/plugin-proposal-private-methods is deprecated

The config throws deprecation warnings

Plugin names that moved from proposal to transform during Babel 7 and 8, left in the config alongside their replacements or pinned at outdated versions.

Plugin names current, warnings silent

browserslist: caniuse-lite is outdated

Browser targets drift out of date

A caniuse-lite dependency that has not been updated for a year, which quietly shifts which transforms preset-env thinks are necessary.

Targets refreshed, output honest

Plugin files are not allowed to export objects

A plugin fails to load

A plugin written against an older Babel major, shipping as an object instead of a function. Either the plugin needs upgrading or a wrapper has to be written around it.

Plugin loads under the current Babel major

code generator has deoptimised the styling

Large files trigger the generator fallback

A single file over 500KB that Babel will still transform, but without preserving formatting. Usually an auto-generated bundle being fed back into the build by mistake.

Generated files excluded from transform

Cannot find module '@babel/preset-typescript'

A preset is missing after an upgrade

A Babel 8 upgrade that renamed packages, a monorepo workspace that only installed Babel at the root, or a hoisting edge case that left a nested package without its devDependencies.

Presets resolving in every workspace

Unexpected token (class fields)

Class fields parse where they should not

A tsconfig and a babel config disagreeing about which class features are allowed, usually when TypeScript useDefineForClassFields does not match the Babel plugin's assumeArray setting.

Class fields consistent across both compilers

What we do

Babel help, from one plugin fix to the whole config

Reach out about a single Babel syntax error, or hand us the whole build config and we will rebuild it.

Rescue
A build that errors on a syntax feature, a runtime that throws regeneratorRuntime, or a decorator stage that does not match the code. We get it compiling again before writing anything up.
preset-env tuning
Browserslist query reviewed against your real traffic, transforms narrowed to what the audience needs, and bundle size measured before and after.
Decorator migration
Moving between legacy, stage-2 and TC39 decorators carefully, with a codemod or manual rewrites so the test suite stays honest through the change.
Babel to SWC or esbuild migration
Porting your Babel config to a faster toolchain, keeping the custom plugins that matter, and dropping the ones that were there for compatibility you no longer need.
Upgrade work
Babel 6 to 7 to 8 upgrades rehearsed on a branch, plugin names updated, deprecated options removed, and output compared against the previous build byte for byte.
Managed Tech
Dependency bumps, caniuse-lite refreshes, transform output monitoring, and an engineer to call when a Babel release quietly changes a default.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Babel alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Babel questions

Something else? Call+1 737 727 7327

Should we migrate off Babel?

Usually yes for new work, often yes for existing apps. SWC and esbuild do most of what preset-env does in a fraction of the time, and TypeScript handles its own transforms now. We look at which custom Babel plugins your codebase relies on, port the ones that matter, and only then recommend the swap with an honest comparison of before and after.

Why do my decorators not work after a Babel upgrade?

Babel supports several decorator stages and the default has moved. A config that worked with the legacy stage can parse but emit differently under the new default, breaking metadata-reflecting code like NestJS and TypeORM. Pinning the version and the decoratorsLegacy or version option is usually what makes it behave again.

How do we set the right preset-env targets?

Start from real traffic, not from a convention. A browserslist query generated from your own analytics tells you which browsers actually visit, and that drives the transforms. Over-targeting old browsers costs bundle size and performance; under-targeting breaks real users.

Why does our build throw regeneratorRuntime is not defined?

preset-env is transpiling async functions down for older targets without the runtime that those transforms depend on. Installing @babel/runtime and @babel/plugin-transform-runtime, or bumping the targets so async functions pass through untouched, both fix it. Which one is right depends on what you still need to support.

Is Babel still worth learning?

If you maintain anything older than a couple of years, yes. The config in front of you is not going away, and understanding how preset-env, plugins and runtime work makes the difference between a safe upgrade and a mystery regression. If you are starting a greenfield project in 2026, you can usually avoid it.

How much does Babel help cost?

An estimate comes back for free. Send us the config, the error output and the Babel versions in play, and a price is ready before any code moves.

Free estimate

Babel giving you trouble?

Send us the babel.config.js, the plugin versions and the build error. A person replies with a quote, and nothing begins until you say the word.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.