Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sam Richard
    @Snugug
    I've got an idea
    David Manning
    @dlmanning
    yes?
    Sam Richard
    @Snugug
    Same model as jQuery, so defaults to async, but can choose to call sass.sync instead
    I'll mock it up tonight
    David Manning
    @dlmanning
    Yeah, that's basically how it worked before
    There was an option to pass in
    Sam Richard
    @Snugug
    Yah, but I don't want an option
    David Manning
    @dlmanning
    Oh, because you don't like the idea of a function sometimes behaving synchronously and sometimes asynchronously?
    Sam Richard
    @Snugug
    Yah, kinda. Note that I want it to be more explicit than a hashed option. I'd like to keep the options hash as clear as possible and something we can pass straight through
    Don't want to conflate rendering options as specified by the compiler with ours
    David Manning
    @dlmanning
    That makes sense to me
    Sam Richard
    @Snugug
    Cool. I just got in. I'm going to write this PR up
    Sam Richard
    @Snugug
    @dlmanning dlmanning/gulp-sass#224
    Call sass.sync if you want sync compiling; just calling sass will compile async
    Simon
    @sp90

    Hey guys

    Why don't we run node-sass 3.0.0 beta yet? is there a reason other than its a beta?

    Sam Richard
    @Snugug
    @sp90 the 2.x branch will let you. There were some breaking changes that had to be made to support it
    We will be releasing a beta soon from that branch, but until then you can install directly from that branch
    Simon
    @sp90
    @Snugug thanks man, working on an animation lib that utilize the :at-root
    Honza Bittner
    @tenhobi
    Hi guys, does anybody know how to fix sass/node-sass#829 ?
    Sam Richard
    @Snugug
    @hobi It's a Libsass issue, pointed you the relevant fix there, and the progress in node-sass
    Honza Bittner
    @tenhobi
    Ahh, I was a little bit confused. :) So I will create the issue in Libsass and add the link to sass/node-sass#829...
    ... I see they already have this similar issue.
    Andrew Martin
    @andrewmartin
    Anyone alive in here?
    Was curious if anyone was having issues with gulp-sourcemaps
    gulp.task('styles', function() { return gulp.src(config.paths.styles) .pipe(sourcemaps.init()) .pipe(sass()) .pipe(sourcemaps.write()) .pipe(gulp.dest('public/css')) .pipe(rename('application.min.css')) .pipe(uglifycss()) .pipe(gulp.dest('public/css')) .pipe(livereload()) .on('error', gutil.log); });
    agh, didn't paste well, but my task is fairly simple
    Whoops, looks like latest version of gulp-sass fixed it! :)
    Sorry! :shipit:
    Teun Kelting
    @Steun
    Having trouble, anyone know a fix? sass/node-sass#939
    Pavel
    @pashaigood
    Hi to all! I think, it`s most frequent question, but, can i use sass, not scss?
    Sam Richard
    @Snugug
    Yes
    Pavel
    @pashaigood
    where can i find docs?
    and examples?
    Michael Mifsud
    @xzyfer
    @pashaigood set indentedSyntax: true
    Cam Song
    @camsong
    having trouble
    [21:38:47] [gulp-sass] src/sass/component/_button.scss 230:38 error parsing interpolated value
    the error was caused by using @each in sass
    Raised a issue about this. dlmanning/gulp-sass#277
    Pavel
    @pashaigood
    Hi to all! Sorry for offtop, but i don`t know more a better place for this question. Where can i find copmass lib without ruby?
    Raimo Pitkänen
    @rapitkan
    Hi everyone! I think I have found a bug.
    David Manning
    @dlmanning
    @Snugug : Did you unpublish gulp-sass 2.0.1 ?
    Sam Richard
    @Snugug
    @dlmanning Started to after publishing the new version, cancelled immediately but it looks like it went through. Looking at how to undo it now
    David Manning
    @dlmanning
    @Snugug : I don't think it can be undone
    publish / unpublish is immutable
    Could you just bring the repo up to date with the latest published version?
    Sam Richard
    @Snugug
    It is
    David Manning
    @dlmanning
    @Snugug : package.json in master says 2.0.2
    er says 2.0.1
    Sam Richard
    @Snugug
    Does it? Did I forget to push the number bump?
    Ugh, forgot to push the tag/release from the merge this morning when I did it (well, more specifically, accidently pushed to my fork instead of upstream)