Is extract-text-webpack-plugin still maintained?
No — extract-text-webpack-plugin stopped being maintained around February 2018. extract-text-webpack-plugin's own maintainers named mini-css-extract-plugin as the successor.
- Status
- No longer maintained
- Last maintained
- February 2018
- Use instead
mini-css-extract-plugin— on npm- Succession
- Successor named by the maintainers
- Drop-in
- no — expect code changes
- Confidence
- high
What should I use instead of extract-text-webpack-plugin?
extract-text-webpack-plugin's own maintainers named mini-css-extract-plugin as the successor. mini-css-extract-plugin is not a drop-in replacement, so expect to change call sites.
How to migrate from extract-text-webpack-plugin to mini-css-extract-plugin
Replace ExtractTextPlugin.extract({ ... }) rules with MiniCssExtractPlugin.loader at the head of the CSS loader chain and add new MiniCssExtractPlugin({ filename: '[name].css' }).
Why extract-text-webpack-plugin is on this list
extract-text-webpack-plugin never reached a stable webpack 4 release — it stopped at 4.0.0-beta.0 in February 2018, after the last stable 3.0.2 in October 2017 — and webpack-contrib deprecated it on npm in favour of mini-css-extract-plugin. The newer plugin extracts per module rather than per chunk, which is what makes hot reloading and on-demand CSS loading work.
The succession is settled: primary sources agree and the ecosystem has already moved.
extract-text-webpack-plugin alternatives
The dataset lists no second option: mini-css-extract-plugin is where the ecosystem went, and nothing else has meaningful adoption.
Check your own project for extract-text-webpack-plugin
npx dead-deps --all --min-state unmaintained
Run that in the directory holding your lockfile. If extract-text-webpack-plugin 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 extract-text-webpack-plugin (points at mini-css-extract-plugin)npmjs.com
- webpack docs: MiniCssExtractPluginwebpack.js.org
Packages related to extract-text-webpack-plugin
- uglifyjs-webpack-pluginSuccessor named by the maintainers: terser-webpack-plugin · unmaintained since July 2019
- glamorousSuccessor named by the maintainers: @emotion/react · unmaintained since December 2018
- postcss-cssnextSuccessor named by the maintainers: postcss-preset-env · unmaintained since May 2018
- babel-preset-es2015Successor named by the maintainers: @babel/preset-env · unmaintained since April 2017
- create-react-appSuccessor named by the maintainers: vite · unmaintained since February 2025
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.