Gathering detailed insights and metrics for sass
Gathering detailed insights and metrics for sass
The reference implementation of Sass, written in Dart.
npm install sass
Typescript
Module System
Min. Node Version
Node Version
NPM Version
95.9
Supply Chain
100
Quality
95.4
Maintenance
100
Vulnerability
99.6
License
Dart (77.1%)
TypeScript (22.78%)
JavaScript (0.11%)
HTML (0.01%)
Love this project? Help keep it running — sponsor us today! 🚀
Total Downloads
2,204,064,742
Last Day
3,092,039
Last Week
16,046,203
Last Month
67,136,952
Last Year
713,789,121
MIT License
4,032 Stars
2,649 Commits
356 Forks
77 Watchers
26 Branches
75 Contributors
Updated on Feb 13, 2025
Minified
Minified + Gzipped
Latest Version
1.84.0
Package Id
sass@1.84.0
Unpacked Size
5.42 MB
Size
876.83 kB
File Count
36
NPM Version
10.9.2
Node Version
22.13.1
Published on
Feb 06, 2025
Cumulative downloads
Total Downloads
Last Day
3.4%
3,092,039
Compared to previous day
Last Week
4.9%
16,046,203
Compared to previous week
Last Month
44.6%
67,136,952
Compared to previous month
Last Year
15.3%
713,789,121
Compared to previous year
3
1
A pure JavaScript implementation of Sass. Sass makes CSS fun again.
|
![]() |
|
This package is a distribution of Dart Sass, compiled to pure JavaScript
with no native code or external dependencies. It provides a command-line sass
executable and a Node.js API.
You can install Sass globally using npm install -g sass
which will provide
access to the sass
executable. You can also add it to your project using
npm install --save-dev sass
. This provides the executable as well as a
library:
1const sass = require('sass'); 2 3const result = sass.compile(scssFilename); 4 5// OR 6 7// Note that `compileAsync()` is substantially slower than `compile()`. 8const result = await sass.compileAsync(scssFilename);
See the Sass website for full API documentation.
Dart Sass also supports an older JavaScript API that's fully compatible with
Node Sass (with a few exceptions listed below), with support for both the
render()
and renderSync()
functions. This API is considered deprecated
and will be removed in Dart Sass 2.0.0, so it should be avoided in new projects.
Sass's support for the legacy JavaScript API has the following limitations:
Only the "expanded"
and "compressed"
values of outputStyle
are
supported.
Dart Sass doesn't support the precision
option. Dart Sass defaults to a
sufficiently high precision for all existing browsers, and making this
customizable would make the code substantially less efficient.
Dart Sass doesn't support the sourceComments
option. Source maps are the
recommended way of locating the origin of generated selectors.
Dart Sass, from which this package is compiled, can be used either as a stand-alone executable or as a Dart library. Running Dart Sass on the Dart VM is substantially faster than running the pure JavaScript version, so this may be appropriate for performance-sensitive applications. The Dart API is also (currently) more user-friendly than the JavaScript API. See the Dart Sass README for details on how to use it.
Node Sass, which is a wrapper around LibSass, the C++ implementation of Sass. Node Sass supports the same API as this package and is also faster (although it's usually a little slower than Dart Sass). However, it requires a native library which may be difficult to install, and it's generally slower to add features and fix bugs.
There are a few intentional behavioral differences between Dart Sass and Ruby Sass. These are generally places where Ruby Sass has an undesired behavior, and it's substantially easier to implement the correct behavior than it would be to implement compatible behavior. These should all have tracking bugs against Ruby Sass to update the reference behavior.
@extend
only accepts simple selectors, as does the second argument of
selector-extend()
. See issue 1599.
Subject selectors are not supported. See issue 1126.
Pseudo selector arguments are parsed as <declaration-value>
s rather than
having a more limited custom parsing. See issue 2120.
The numeric precision is set to 10. See issue 1122.
The indented syntax parser is more flexible: it doesn't require consistent indentation across the whole document. See issue 2176.
Colors do not support channel-by-channel arithmetic. See issue 2144.
Unitless numbers aren't ==
to unit numbers with the same value. In
addition, map keys follow the same logic as ==
-equality. See
issue 1496.
rgba()
and hsla()
alpha values with percentage units are interpreted as
percentages. Other units are forbidden. See issue 1525.
Too many variable arguments passed to a function is an error. See issue 1408.
Allow @extend
to reach outside a media query if there's an identical
@extend
defined outside that query. This isn't tracked explicitly, because
it'll be irrelevant when issue 1050 is fixed.
Some selector pseudos containing placeholder selectors will be compiled where they wouldn't be in Ruby Sass. This better matches the semantics of the selectors in question, and is more efficient. See issue 2228.
The old-style :property value
syntax is not supported in the indented
syntax. See issue 2245.
The reference combinator is not supported. See issue 303.
Universal selector unification is symmetrical. See issue 2247.
@extend
doesn't produce an error if it matches but fails to unify. See
issue 2250.
Dart Sass currently only supports UTF-8 documents. We'd like to support more, but Dart currently doesn't support them. See dart-lang/sdk#11744, for example.
Disclaimer: this is not an official Google product.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
Project has not signed or included provenance with any releases.
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-02-03
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More