-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make this package implementation-agnostic #694
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,7 +13,7 @@ Only [Active LTS and Current releases][1] are supported. | |
# Install | ||
|
||
``` | ||
npm install gulp-sass --save-dev | ||
npm install node-sass gulp-sass --save-dev | ||
``` | ||
|
||
# Basic Usage | ||
|
@@ -26,6 +26,8 @@ Something like this will compile your Sass files: | |
var gulp = require('gulp'); | ||
var sass = require('gulp-sass'); | ||
|
||
sass.compiler = require('node-sass'); | ||
|
||
gulp.task('sass', function () { | ||
return gulp.src('./sass/**/*.scss') | ||
.pipe(sass().on('error', sass.logError)) | ||
|
@@ -45,6 +47,8 @@ You can also compile synchronously, doing something like this: | |
var gulp = require('gulp'); | ||
var sass = require('gulp-sass'); | ||
|
||
sass.compiler = require('node-sass'); | ||
|
||
gulp.task('sass', function () { | ||
return gulp.src('./sass/**/*.scss') | ||
.pipe(sass.sync().on('error', sass.logError)) | ||
|
@@ -56,9 +60,36 @@ gulp.task('sass:watch', function () { | |
}); | ||
``` | ||
|
||
You can choose whether to use [Dart Sass][] or [Node Sass][] by setting the `sass.compiler` property. Node Sass will be used by default, but it's strongly recommended that you set it explicitly for forwards-compatibility in case the default ever changes. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The explicit compiler would be a breaking change and probably dealt with then instead of recommending it now. I'm just thinking if the future change happens it might be through a different method and this locks in the API when it's not needed yet There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One way or another, there needs to be a way of overriding the compiler. That's the whole point of this change. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Technically overriding the compiler is already possible. Who knows what folks are doing with it. I'm OK with this because now we're at least documenting it as part of the API so we're committed to version correctly if we change. |
||
|
||
[Dart Sass]: http://sass-lang.com/dart-sass | ||
[Node Sass]: https://github.com/sass/node-sass | ||
|
||
Note that when using Dart Sass, **synchronous compilation is twice as fast as asynchronous compilation** by default, due to the overhead of asynchronous callbacks. To avoid this overhead, you can use the [`fibers`](https://www.npmjs.com/package/fibers) package to call asynchronous importers from the synchronous code path. To enable this, pass the `Fiber` class to the `fiber` option: | ||
|
||
```javascript | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe mention the |
||
'use strict'; | ||
|
||
var Fiber = require('fibers'); | ||
var gulp = require('gulp'); | ||
var sass = require('gulp-sass'); | ||
|
||
sass.compiler = require('sass'); | ||
|
||
gulp.task('sass', function () { | ||
return gulp.src('./sass/**/*.scss') | ||
.pipe(sass({fiber: Fiber}).on('error', sass.logError)) | ||
.pipe(gulp.dest('./css')); | ||
}); | ||
|
||
gulp.task('sass:watch', function () { | ||
gulp.watch('./sass/**/*.scss', ['sass']); | ||
}); | ||
``` | ||
|
||
## Options | ||
|
||
Pass in options just like you would for [`node-sass`](https://github.com/sass/node-sass#options); they will be passed along just as if you were using `node-sass`. Except for the `data` option which is used by gulp-sass internally. Using the `file` option is also unsupported and results in undefined behaviour that may change without notice. | ||
Pass in options just like you would for [Node Sass](https://github.com/sass/node-sass#options); they will be passed along just as if you were using Node Sass. Except for the `data` option which is used by gulp-sass internally. Using the `file` option is also unsupported and results in undefined behaviour that may change without notice. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should some validation around the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nothing about this behavior is changing. I just slightly reformatted the paragraph to refer to Node Sass more consistently. |
||
|
||
For example: | ||
|
||
|
@@ -111,10 +142,13 @@ gulp.task('sass', function () { | |
|
||
# Issues | ||
|
||
`gulp-sass` is a very light-weight wrapper around [`node-sass`](https://github.com/sass/node-sass), which in turn is a Node binding for [`libsass`](https://github.com/sass/libsass), which in turn is a port of [`Sass`](https://github.com/sass/sass). Because of this, the issue you're having likely isn't a `gulp-sass` issue, but an issue with one of those three projects. | ||
`gulp-sass` is a very light-weight wrapper around either [Dart Sass][] or [Node Sass][] (which in turn is a Node binding for [LibSass][]). Because of this, the issue you're having likely isn't a `gulp-sass` issue, but an issue with one those projects or with [Sass][] as a whole. | ||
|
||
[LibSass]: https://sass-lang.com/libsass | ||
[Sass]: https://sass-lang.com | ||
|
||
If you have a feature request/question how Sass works/concerns on how your Sass gets compiled/errors in your compiling, it's likely a `libsass` or `Sass` issue and you should file your issue with one of those projects. | ||
If you have a feature request/question how Sass works/concerns on how your Sass gets compiled/errors in your compiling, it's likely a Dart Sass or LibSass issue and you should file your issue with one of those projects. | ||
|
||
If you're having problems with the options you're passing in, it's likely a `node-sass` or `libsass` issue and you should file your issue with one of those projects. | ||
If you're having problems with the options you're passing in, it's likely a Dart Sass or Node Sass issue and you should file your issue with one of those projects. | ||
|
||
We may, in the course of resolving issues, direct you to one of these other projects. If we do so, please follow up by searching that project's issue queue (both open and closed) for your problem and, if it doesn't exist, filing an issue with them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it is still the included default this doesn't need to change