Skip to content
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

Crash on scss error when using source maps #73

Closed
floscr opened this issue Jul 25, 2014 · 9 comments
Closed

Crash on scss error when using source maps #73

floscr opened this issue Jul 25, 2014 · 9 comments
Milestone

Comments

@floscr
Copy link

floscr commented Jul 25, 2014

When I use gulp-sass with sourcemaps the errors don't get logged to the console anymore and gulp just crashes.

My config:

var options = {};

options.sass = {
    errLogToConsole: true,
    sourceComments: 'map',
    sourceMap: 'scss'
}

// Styles for development
// libSASS & Autoprefixer
// [gulp-sass](https://www.npmjs.org/package/gulp-sass)
// [gulp-autoprefixer](https://www.npmjs.org/package/gulp-autoprefixer)
gulp.task('styles-dev', function() {
  return gulp.src(scss_src_dir + '/style.scss')
    .pipe(plugins.sass(options.sass))
    .pipe(plugins.autoprefixer('last 2 versions', 'ie 9', 'ios 6', 'android 4'))
    .pipe(gulp.dest(scss_dst_dir))
    .pipe(browserSync.reload({stream:true}));
});

The error returned:
60543 segmentation fault gulp

@bobeagan
Copy link

It works fine for me with sourceMap : 'sass' but having sourceComments: 'map' is what causes it to crash for me. If I set sourceComments: 'none' then it works as expected.

@chrisspiegl
Copy link

+1 I would like to see this fixed. I tested it with the same effects as @bobeagan.

@floscr
Copy link
Author

floscr commented Jul 29, 2014

But without sourceComments, where would the Browser get the sourceMap information?

@chrisspiegl
Copy link

@artish that is the problem. As far as I tested it, the segmentation fault always appears no matter if you try writing the sourcemaps to a file or in the comments.

@yantakus
Copy link

Look how gulp-less cope with this problem. They use gulp-sourcemaps to handle source maps. Maybe we can also look this way?

@subblue
Copy link

subblue commented Sep 11, 2014

+1 to also see this fixed.
sourceComments: 'map' always causes a Segmentation fault: 11 when there is an error in the .scss no matter what work arounds I try.

@Arkkimaagi
Copy link

I think this could be caused by this: sass/node-sass#378

I could be wrong tho.

@Snugug
Copy link
Collaborator

Snugug commented Mar 31, 2015

This has been resolved in 2.x. We have moved to using gulp-sourcemaps like suggested earlier in this thread. Please try it and report back. If we don't hear back, we'll assume it's been resolved and close this issue.

npm install dlmanning/gulp-sass#2.x

@Snugug Snugug added the bug label Mar 31, 2015
@Snugug Snugug added this to the 2.0.0 milestone Mar 31, 2015
@Snugug
Copy link
Collaborator

Snugug commented Apr 30, 2015

As it's been a month, I'm closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants