Is @zeit/next-sass still maintained?
No — @zeit/next-sass stopped being maintained around March 2020. @zeit/next-sass's functionality was absorbed into next.
- Status
- No longer maintained
- Last maintained
- March 2020
- Use instead
next— on npm- Succession
- Absorbed elsewhere
- Drop-in
- no — expect code changes
- Confidence
- high
What should I use instead of @zeit/next-sass?
@zeit/next-sass's functionality was absorbed into next. next is not a drop-in replacement, so expect to change call sites.
How to migrate from @zeit/next-sass to next
Remove the plugin from next.config.js, add sass as a devDependency, and import .scss files directly from components; put global styles in pages/_app.
Why @zeit/next-sass is on this list
Next.js added built-in CSS support in 9.2 and built-in Sass support in 9.3 (March 2020), which made the next-css and next-sass plugins unnecessary; the 9.3 release post explicitly recommends removing @zeit/next-sass from next.config.js and package.json. The package carries an npm deprecation notice pointing at the built-in support, its last release was in September 2018, and the @zeit scope itself was retired when the company became Vercel.
The succession is settled: primary sources agree and the ecosystem has already moved.
@zeit/next-sass alternatives
Beyond the primary recommendation, these are credible for @zeit/next-sass's use case:
sass— view on npm
Check your own project for @zeit/next-sass
npx dead-deps --all --min-state unmaintainedRun that in the directory holding your lockfile. If @zeit/next-sass 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 @zeit/next-sass (points at Next.js built-in Sass support)npmjs.com
- Next.js 9.3 release notes: built-in Sass support, "we recommend removing the plugin"nextjs.org
- Next.js CSS documentationnextjs.org
Packages related to @zeit/next-sass
- node-sassReimplementation: sass · unmaintained since July 2024
- node-sass-chokidarReplacement project: sass · unmaintained since June 2022
- create-react-appSuccessor named by the maintainers: vite · unmaintained since February 2025
- puppeteer-firefoxAbsorbed elsewhere: puppeteer · unmaintained since January 2020
- @angular/httpAbsorbed elsewhere: @angular/common · unmaintained since May 2019
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.