Always receiving "Extension host terminated unexpectedly"

[dineiar]

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

[Abourass]

Same and its all Sass extensions, not just this one. I tried installing node-sass globally, hoping perhaps it was that. It was not.

[Tigerlady]

I too am having this issue.

[SimonMayerhofer]

Same. Seems like it can't handle comments like this:

//@import "plugins/xxx";

at least that's was the problem at my side.

[ghost]

also having issues, but only after vs code updated.

[samirdjelal]

Same here, after latest vscode update it seems stopping with the same error

[davidcsida]

I'm also experiencing the same problem when using @import.

[davidcsida]

I'm also experiencing the same problem when using @import.

I found out that crashes only happen while writing @import. If I finish writing the path and restart the extensions, everything works perfectly.

[samirdjelal]

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

[yehudaTiram]

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."

[norixx]

@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.

[yehudaTiram]

I guess both can't work together.

[FelesNoctis]

This should be resolved with Image Preview 0.17.4. My environment's working correctly again with both enabled.

https://github.com/kisstkondoros/gutter-preview/issues/40

[mattgriffiths4]

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!

[eteisman]

I now have the same issue. One very similar project is OK, the other crashes. But I absolutely cant make sense of why this is happening at all.

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 am unable to figure out why the sass-compiler crashes in one directory, yet compiles in the other.

[mizhon]

Image Preview

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.

[SmithWebDev]

My issue was with the Live Sass Compiler... once uninstalled, no longer had the same extension host error

[FelesNoctis]

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 can confirm that I've been having this issue again, and only with files with @import. Specifically, in the project I'm working on, these imports work perfectly fine due to the environment configuration (as in, the program in question utilizes them just fine), but that environment is also non-standard. Effectively, the program itself is reading the core SCSS files from one folder and using those import paths as a reference, and then has a different folder outside of that path that actually has the files. VSCode is confused as all hell, but the program knows what its doing.

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: https://github.com/sergiirocks/vscode-ext-color-highlight/issues/53

[FelesNoctis]

As an example:

css/bootstrap/_bootstrap.scss targeting files within css/bootstrap/bootstrap/ This works entirely as expected within VSCode, no extension issues.

css/bootstrap.scss targeting files within css/bootstrap/bootstrap/ Explosions, lasers, death, destruction, and the extension host failing.

As above, the second example above works fine within the program itself for various reasons, but VSCode isn't aware of that environment so it has a seizure. And no, I have no idea why the project is set up this way.

---

This isn't the first time I've run into an issue with another extension making Live SASS Compiler eat itself and take the extension host with it, which, as above, is why I'm surprised there isn't an error catch for this sort of thing implemented. It shouldn't burn the house down for a roach.

[ErSulba]

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

[PiotrGrzy]

Same thing here, happes only when using @import...Anyone solved this problem?

[airosu]

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

"color-highlight.languages": [ "*", "!scss" ]

[russmatt]

Apparently solved disablingthe extension and re-enabling it after opening the project.

[ZippoLee12138]

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

"color-highlight.languages": [ "*", "!scss" ]

Thank you!

[zhaluza]

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

"color-highlight.languages": [ "*", "!scss" ]

This seems to fix it for me — thanks!

[SuiYoung]

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

"color-highlight.languages": [ "*", "!scss" ]

Thank you for this! There's an extension conflict with "color highlight" extension. This addition to settings.json fixed the issue. No more crashes.

[alimertcakar]

adding an empty /* */ end of a scss file crashes the extension also.

[sumandeveloping]

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

"color-highlight.languages": [ "*", "!scss" ]

It worked for me superbly.....

[power-f-GOD]

For me, the issue was caused by Live Sass Compiler. If it's same with you, do these:

1. Reload extension host;
2. Uninstall LSC;
3. Reload VS Code;

That should fix the error. If you need something like LSC, do the following:

4. Install node-sass globally with npm i -g node-sass;
5. Then run (in watch mode) with node-sass -w --output-style=compressed path/to/file.scss path/to/file.min.css; and it's way faster than LSC in compilation. Note that the watch and output-style flags are optional.

PS: You can add a "sass" prop/key in the "scripts" section of "package.json" and assign it a value of the script to run: node-sass -w --output-style=compressed path/to/file.scss path/to/file.min.css; with that you can then run npm run sass from your project directory to compile your SCSS file(s).

https://www.npmjs.com/package/node-sass#command-line-interface

[shubhdevelop]

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

"color-highlight.languages": [ "*", "!scss" ]

Thanks man this seriously made my day, I was googling some solution for hours worked for me!

[jibaraakira]

For my "Extension host terminated unexpectedly" , console error says TypeError : cannot read property 'length' of undefined .

This error occurred even after setting “ color-highlight.languages ”: [“ * ”,“! Scss ”] to setting.json.