# Install node-sass with Homebrew, chocolatey, Nix, pacman, scoop JavaScript implementation of a Sass compiler. Version 1.102.0 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#sass. ## Install ```sh sudo av install brew:node-sass ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install node-sass ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#sass ``` Evidence: nixpkgs package indexes: pkgs/by-name/sa/sass/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S dart-sass ``` Evidence: Arch Linux sync databases: dart-sass from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - Chocolatey (92%): ```sh choco install sass ``` Evidence: Chocolatey community package catalog: sass from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','samsung-magician' - Scoop (92%): ```sh scoop install main/sass ``` Evidence: Scoop official bucket manifest trees: bucket/sass.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:node-sass - **Package manager:** Homebrew - **Version:** 1.102.0 - **Source summary:** JavaScript implementation of a Sass compiler - **Homepage:** - **Last updated:** 2026-07-26T03:56:13Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - sass (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.102.0 ## Project history and usage The Homebrew formula named node-sass now points at Dart Sass rather than the retired `node-sass` LibSass wrapper. Homebrew describes the formula as a JavaScript implementation of a Sass compiler and links it to `sass/dart-sass`, with the `sass` executable as the practical package surface. ### Project history The historical `node-sass` npm package was a Node.js wrapper around LibSass. The Sass team wrote on 26 October 2020 that LibSass and packages built on top of it, including Node Sass, were deprecated because LibSass lacked enough maintainer bandwidth to keep up with Sass and CSS language changes. Dart Sass 1.0.0 was released on 26 March 2018. The Sass team described that release as the first stable Dart Sass release, published to GitHub, npm, Chocolatey, Homebrew, and pub, with compatibility with the Sass spec test suite and broad compatibility with the Node Sass API. On 24 July 2024 the Sass team declared Node Sass end-of-life, marked the npm package deprecated, archived its GitHub repository, and recommended migration to Dart Sass. The same post notes that there is no longer an officially supported way to use LibSass from Node.js. ### Adoption history Node Sass mattered because it made Sass common outside the original Ruby ecosystem, especially in JavaScript build pipelines that wanted a fast native compiler. Its retirement was not just a package rename: it marked the JavaScript ecosystem's shift from LibSass bindings to Dart Sass as the maintained reference implementation. Homebrew Formulae lists node-sass 1.101.0, linked to Dart Sass, with 3,447 installs over 365 days and 3,259 installs on request. That residual use mostly represents people installing a familiar package name to get the maintained `sass` compiler rather than adopting the old Node Sass binding. ### How it is used For new work, package nerds treat this as Dart Sass: run `sass input.scss output.css`, use watch/build scripts, or depend on the JavaScript API from the `sass` package. The Dart Sass README shows `npm install -g sass` for a global executable and `npm install --save-dev sass` for project use, then `require('sass')` and `sass.compile(...)` from Node. For legacy migrations, the Sass team's short path is to replace `node-sass` in `package.json` with `sass`. Most old `render()` and `renderSync()` callers continue through Dart Sass's legacy JavaScript API, but new code should use the newer compile API because the legacy API is deprecated for Dart Sass 2.0.0. ### Why package nerds care This formula is a naming fossil. It preserves the ecosystem memory of Node Sass while delivering Dart Sass, and it is useful precisely because build tools, READMEs, and muscle memory often say `node-sass` even after the maintained compiler moved on. ### Related projects - Dart Sass - LibSass - Ruby Sass - sass npm package - sass-embedded ### Sources - - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Other Package-Manager Records - Nix - sass: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/sa/sass/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman - dart-sass - 1.102.0-1: installed executable or alias match | Arch Linux sync databases: dart-sass from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Sass makes CSS fun again | http://sass-lang.com/ - Chocolatey - sass: installed executable or alias match | Chocolatey community package catalog: sass from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','samsung-magician' - Scoop - main/sass: installed executable or alias match | Scoop official bucket manifest trees: bucket/sass.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/node-sass.yml](https://github.com/mxcl/pkgdb/blob/main/combined/node-sass.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph