Currently options are leaking between compilation runs. This is most
evident when using an array of importers. The array is shallow copied
internally, and the children of that array are wrapped by Node Sass.
When the next file is compiled the options are shallow copied once
again however this time the importer array contains the wrapped
importers not the original ones.
Instead of shallow copying with `Object.assign` this patch does a
full deep clone. Node Sass should also do this to prevent mutating
the options being passed in.
Related sass/node-sass#1168
Fixes#467 (probably)
I believe this was mistakenly removed in #353.
@eoneill can you shed some light on why you removed this? It has
caused issues for users.
Fixes#469Fixes#473
I changed var srcs to filteredSources to be more semantic and closer to the existing formatting. I moved the var declaration to the top level in an attempt to comply with the established coding standards.
Some of our dev dependencies are at least a major version behind.
This require update required updating our .eslintrc config because
some of the rules we used have been removed.
Currently if the input file is blank we bail out early, returning
the input file object. This causes gulp to simply copy the input
Sass file. We instead need to rewrite the file extension to .css.
Fixes#352
This will let you write sass.compiler.types, for example, and access the
sass types without having to require it in your main app.
Additionally, this lets you use a forked compiler, or a different branch
of the same compiler.
Aligns with Stylish reporter (used in ESLint, jshint-stylish, etc…
Removed colors from message except for which is a standard Gulp log output color
Includes line and column in error report
Addes `sass.sync` to allow users to compile synchronously.
Wrapped the async callback in an `if` statement controlled by a `sync` option for the main function
Added `renderSync` render option
# By Vincent Prouillet
# Via Vincent Prouillet
* '2-sourcemaps' of https://github.com/Keats/gulp-sass:
Sourcemap paths seem to be relative now?
# Conflicts:
# index.js
At least the test still pass and paths
looks the same with and without the relative fudge.
Sourcemaps are completely wonky though and do not point at the right thing
Also removes jshint since it's using eslint now
Simply pass everything to node-sass and just hand
back the results to gulp.
Removed custom options like success/failure cb
and sync rendering.
Missing:
- gulp-sourcemaps support + test