-
Notifications
You must be signed in to change notification settings - Fork 169
Always receiving "Extension host terminated unexpectedly" #112
Comments
Same and its all Sass extensions, not just this one. I tried installing node-sass globally, hoping perhaps it was that. It was not. |
I too am having this issue. |
Same. Seems like it can't handle comments like this:
at least that's was the problem at my side. |
also having issues, but only after vs code updated. |
Same here, after latest vscode update it seems stopping with the same error |
I'm also experiencing the same problem when using @import. |
I don't use @import at all but i still get that crash, even that i made my scss empty again to findout if the file is content crashing the ext, but it even crash on empty file. while I changed the priject to find out that it works on some projects |
In my case the problem was solved by removing "Image Preview" Extension. For some reason it caused live-sass-compiler to generate "Extension host terminated unexpectedly." |
@yehudaTiram It worked for me too. Some code confliction?? I cannot tell which extension causes this error, I've removed 'Image Preview' for the time being. |
I guess both can't work together. |
This should be resolved with Image Preview 0.17.4. My environment's working correctly again with both enabled. |
Is anyone else still having this issue? Every time I start writing @import in my main.scss file it crashes the sass-compiler extension? I don't have the image preview extension installed either... really annoying! |
I now have the same issue. One very similar project is OK, the other crashes. Update: I am no longer able to build my project. It is broken, and no idea why!!! Update 2: After re-creating my workspace from GIT, the sass-compiler works again. |
I don't install the "Image preview" extension but still get the same crash error. So I think that's not the common method to fix this issue. |
My issue was with the Live Sass Compiler... once uninstalled, no longer had the same extension host error |
I can confirm that I've been having this issue again, and only with files with That being said, obviously it's difficult for Live SASS Compiler, or anybody else for that matter, to adapt to strange environments like that. However I AM surprised that an error catch hasn't been designed yet. LSC shouldn't be so brittle that another extension can kill it. Also see: |
i'm having the same error while the highlight-colors and live-sass-compiler extensions are running, it's kinda annoying since you have deactivate the highlight colors extension if you want to continue using the sass compiler |
Same thing here, happes only when using @import...Anyone solved this problem? |
I am also having this issue running both live sass compiler and color highlight extensions. I was able to fix this by setting the supported languages for color-highlight to everything except for scss in settings.json
|
Apparently solved disablingthe extension and re-enabling it after opening the project. |
Thank you! |
This seems to fix it for me — thanks! |
Thank you for this! |
adding an empty /* */ end of a scss file crashes the extension also. |
It worked for me superbly..... |
For me, the issue was caused by Live Sass Compiler. If it's same with you, do these:
That should fix the error. If you need something like LSC, do the following:
PS: You can add a https://www.npmjs.com/package/node-sass#command-line-interface |
Thanks man this seriously made my day, I was googling some solution for hours worked for me! |
I have resolved this error. As a method, I realized a little by rewriting the js file of "Live Sass Compiler". The process of work until resolution is as follows.
process["on"]("uncaughtException", (function(ex) {
//if (!(ex instanceof ExitStatus)) {
// throw ex
// }
}));
|
Thanks Jibaraakira, I follow your way and seems it works! |
In case anyone is still having problems with the extension, I've noticed that if I use @import with the wrong address it'll cause the extension to terminate. It's worthy checking it and give it another try. |
I have found this to help with the issue as well ! Thanks Jibaraakira! |
Thank you airosu! |
Thank you so much! It works! |
So this is the solid resolution so far. Thanx @jibaraakira |
Finally a solution that worked for me, thanks a lot |
YEAY very helpful, thanks man... |
Hey guys, @glenn2223 is continuing work on this extension in a new repo at: https://github.com/glenn2223/vscode-live-sass-compiler |
Thank you! It works perfect! |
In my case when i use import "something" its terminated |
Nothing is working in 2021 glen is died..... |
I am still actively maintaining my version of this project, please ignore @fatherofphysics comment |
Improve SASS compiler please very fast it has bugs it cant compile scss. Fix this please kindly @fatherofphysics |
Try my version of this extension. Available at https://marketplace.visualstudio.com/items?itemName=glenn2223.live-sass If you still have problems then open an issue here -> https://github.com/glenn2223/vscode-live-sass-compiler/issues |
@glenn2223 I will give it a shot to your version :) |
thanks bro this solved my problem, I believe that the two extensions conflict and causes this error |
If you use something like 7-1 folder architecture and import files only in /main.scss this setting works even better - color highlight extension can still work in other files without causing this problem. |
thank you sir you made my day |
Please close this issue |
When I open a workspace in VS Code, even without having any scss file open, I'm receiving the message "Extension host terminated unexpectedly". Details:
When the extension is disabled everything works fine.
I have the Live Server extension installed. This is different from #53 , as I'm receiving the error just by opening VS Code.
Reproduced in 2 versions:
VS Code v1.28.0 - commit 431ef9da3cf88a7e164f9d33bf62695e07c6c2a9
VS Code v1.28.2 - commit 7f3ce96ff4729c91352ae6def877e59c561f4850
Environment:
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
The text was updated successfully, but these errors were encountered: