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
Still running Babel?
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.
What it is
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.
The honest version
No technology is all upside. This is where Babel earns its place and where it tends to cause trouble.
Sound familiar?
The Babel problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Reach out about a single Babel syntax error, or hand us the whole build config and we will rebuild it.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
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.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: