Is rollup-plugin-babel still maintained?
No — rollup-plugin-babel stopped being maintained around March 2020. The same project continues under the name @rollup/plugin-babel.
- Status
- No longer maintained
- Last maintained
- March 2020
- Use instead
@rollup/plugin-babel— on npm- Succession
- Renamed package
- Drop-in
- no — expect code changes
- Confidence
- high
What should I use instead of rollup-plugin-babel?
The same project continues under the name @rollup/plugin-babel. @rollup/plugin-babel is not a drop-in replacement, so expect to change call sites.
How to migrate from rollup-plugin-babel to @rollup/plugin-babel
Swap the dependency and import the named export: import { babel } from '@rollup/plugin-babel'. The scoped plugin's README asks you to set babelHelpers explicitly, usually 'bundled' or 'runtime'.
Why rollup-plugin-babel is on this list
Rollup consolidated its first-party plugins into the @rollup scope in 2020 and moved them into the rollup/plugins monorepo. rollup-plugin-babel's last release was 4.4.0 in March 2020 and it is deprecated on npm with a notice pointing at @rollup/plugin-babel. The unscoped node-resolve and commonjs plugins were retired the same way.
The succession is settled: primary sources agree and the ecosystem has already moved.
rollup-plugin-babel alternatives
The dataset lists no second option: @rollup/plugin-babel is where the ecosystem went, and nothing else has meaningful adoption.
Check your own project for rollup-plugin-babel
npx dead-deps --all --min-state unmaintained
Run that in the directory holding your lockfile. If rollup-plugin-babel is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.
Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.
Evidence
Every claim on this page traces to a primary source. Check them:
- npm deprecation notice for rollup-plugin-babel ("Please use @rollup/plugin-babel")npmjs.com
- @rollup/plugin-babel in the rollup/plugins monorepogithub.com
Packages related to rollup-plugin-babel
- babel-eslintRenamed package: @babel/eslint-parser · unmaintained since February 2020
- @hapi/joiRenamed package: joi · unmaintained since March 2020
- babel-preset-es2015Successor named by the maintainers: @babel/preset-env · unmaintained since April 2017
- cucumberRenamed package: @cucumber/cucumber · unmaintained since December 2020
- popper.jsRenamed package: @popperjs/core · unmaintained since January 2020
See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.