Gathering detailed insights and metrics for fast-sass-loader-china2
Gathering detailed insights and metrics for fast-sass-loader-china2
Gathering detailed insights and metrics for fast-sass-loader-china2
Gathering detailed insights and metrics for fast-sass-loader-china2
npm install fast-sass-loader-china2
Typescript
Module System
Node Version
NPM Version
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
91 Commits
1 Watchers
1 Branches
1 Contributors
Updated on Oct 31, 2018
Latest Version
1.4.6
Package Id
fast-sass-loader-china2@1.4.6
Unpacked Size
23.49 kB
Size
8.15 kB
File Count
11
NPM Version
5.6.0
Node Version
8.9.4
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Blazingly fast sass loader for webpack.
Tips: using with fast-css-loader you will get more than 10 times css build performance
Features:
sass-loader
in large sass project@import
same file in different placeurl(...)
(see https://github.com/webpack-contrib/sass-loader#problems-with-url)fast sass loader for webpack. 5~10 times faster than sass-loader, and support url resolve.
sass-loader
Features | fast-sass-loader | sass-loader |
---|---|---|
Performance | Fast (5~10 times) | Slow |
Sass Dedupe | ✓ | × |
Url Resolve | ✓ | × (need resolve-url-loader, it's buggy) |
Loader Config | × | ✓ |
Source Map | × | ✓ |
Internal Cache | ✓ | × |
performance benchmark (run npm run perf
):
Since the sass-loader
doesn't dedupe repeated sass files, the result will be very very large (6.95MB!!!), and the total compile time takes 64.9 seconds (nearly 6 times longer than fast-sass-loader
).
fast-sass-loader
is faster than sass-loader
?node-sass
won't compile same file repeatedly, the performance improvement is s ignificant when your sass files number grows very large.fast-sass-loader
will merge all sass files into a single file, so node-sass only need to compile one large file, it's faster than @importer
of libsass.install by npm:
1npm install fast-sass-loader --save-dev
and you need install node-sass and webpack as peer dependencies.
{
module: {
rules: [
{
test: /\.(scss|sass)$/,
use: [
'css-loader',
{
loader: 'fast-sass-loader',
options: {
includePaths: [ ... ]
}
}
]
},
// other loaders ...
]
}
}
{
module: {
loaders: [
{
test: /\.(scss|sass)$/,
loader: 'css!fast-sass'
},
// other loaders ...
]
}
}
An array of paths that node-sass can look in to attempt to resolve your @import declarations. When using data, it is recommended that you use this.
If you want to prepend Sass code before the actual entry file, you can set the data option. In this case, the loader will not override the data option but just append the entry's content. This is especially useful when some of your Sass variables depend on the environment:
1{ 2 loader: "fast-sass-loader", 3 options: { 4 data: "$env: " + process.env.NODE_ENV + ";" 5 } 6}
Please note: Since you're injecting code, this will break the source mappings in your entry file. Often there's a simpler solution than this.
If you want to import files that aren't basic Sass or css files, you can use the transformers option. This option takes an array of transformer entries, each with a list of file extensions and a tranform function. If an imported file's extension matches one of the transformers' extensions, the file contents will be passed to the corresponding transform function. Your transform function should return a sass string that will be directly written into your compiled Sass file. This is especially useful if you use .json files to share your basic styles across platforms and you'd like to import your .json files directly into your Sass.
1{ 2 loader: "fast-sass-loader", 3 options: { 4 transformers: [ 5 { 6 extensions: [".json"], 7 transform: function(rawFile) { 8 return jsonToSass(rawFile); 9 } 10 } 11 ] 12 } 13}
.scss
and.sass
file is not allowedSince fast-sass-loader
will parse @import
and merge all files into single sass file, you cannot import .scss
file from .sass
(or opposite).
For example:
1// file: entry.scss 2@import "path/to/file.sass"; // cannot import `path/to/file.sass` in a `.scss` file 3 4body { 5 background: #FFF; 6}
Since fast-sass-loader
will dedupe sass file, later imported file will be ignored. Using same variable name in different sass fill would produce unexpected output.
For example (compile entry.scss
with fast-sass-loader):
1// a.scss 2$foobar: #000;
1// b.scss 2@import "a.scss"; 3$foobar: #AAA; 4 5h1 { color: $foobar; }
1// entry.scss 2@import "b.scss"; 3@import "a.scss"; // this file will be ignore: $foobar === #AAA 4 5h2 { color: $foobar; } 6 7// will output: 8// h1 { color: #AAA; } 9// h2 { color: #AAA; }
You can use variable prefix to bypass.
fast-sass-loader doesn't support @import
statement in sass rules, for example:
1.a { 2 @import 'group' 3} 4 5.b { 6 @import 'group' 7}
you should wrap the rules that you want to import with mixin, then include them in your .a { ... }
or .b { ... }
MIT
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2025-07-07
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