-
-
Notifications
You must be signed in to change notification settings - Fork 426
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
Abort trap: 6 #65
Comments
I'm also getting this. |
Yep, I was also getting these. You need to stick with sass-loader |
So close! The brief 30 seconds of custom importers was bliss. |
+1 for this. =) |
+1 |
Also seeing the same behaviour. |
+1 had to back up to [email protected] because 0.5.0 has a dependency on [email protected] which doesn't exist |
Thanks for the fix here @andycmaj, struggling with the same issue! |
I've managed to write a version of sass-loader that provides the same features while depending on node-sass |
@jhnns I'm still seeing this problem even with |
Just wanted to iterate that this loader has been extremely troublesome for me. Slowing me down massively. Sometimes it works but mostly it crashes. At least i know what's causing it. |
I didn't expect |
For those still looking for a workaround: The latest working version seems to be |
Afaik |
Unfortunately |
For those of you trying to get this to work, you need to use |
Same here; I had to downgrade to sass/node-sass@fce0993 allegedly fixes this issue, however even when using it, I kept getting random crashes with both |
@raphaelsaunier I've updated the README |
This seems totally stable for me now with the latest node-sass release - and pulling I haven't tested with a large codebase full of imports yet, but I will likely get to it over the weekend. |
@haustraliaer that are good news. Please let me know if everything works as expected. I'll remove the note in the README then. |
This should probably be a separate issue, but after upgrading to 1.0.2 webpack will just completely hang. |
Yeah I'm on 1.0.0 so haven't seen that bug - you should log it separately. |
@alexduan this does not happen in our tests, so please try to narrow it down and open a separate issue. |
After upgrading to 1.0.0 I'm getting fairly inconsistent errors along the lines of:
Seems to be an issue with node-sass that has persisted into the pre-release sass-loader is using?
sass/node-sass#713
The text was updated successfully, but these errors were encountered: