vscode-live-sass-compiler: Unhandled error when path is not found - (Renamed from command fail)

After Updating VSC to version 1.55.0 the Live compiler stays at ‘Working on it…’ and gives the error: "Running the contributed command: 'liveSass.command.watchMySass' failed."

Version: 1.55.0 Commit: c185983a683d14c396952dd432459097bc7f757f Date: 2021-03-30T16:01:05.981Z Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Darwin x64 20.3.0

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 37 (15 by maintainers)

Commits related to this issue

Fixes - No longer throws error on phantom/non-existent directories ([ #57](https://github.com/glenn2223/vscode-live-sass-compiler/issues/57)) - Errors catching no longer fails when the error is with ... — committed to glenn2223/vscode-live-sass-compiler by glenn2223 3 years ago

Most upvoted comments

Good, I’m glad it works. v5 here we come 🎉

Thanks for your help in debugging this.

glenn2223 on Apr 6, 2021

So fdir allows you to suppress errors, which it claims to do by default (obviously not 😁)

Can you test this one, which should suppress the error: live-sass-5.0.0-rc.4.4.zip

If this works then I can get v5 released tonight.
FYI: Problems with publishing to VS Code’s marketplace means that I really don’t want to (well, can’t) publish any more RC’s (Ref #54)

glenn2223 on Apr 6, 2021

So the config folder (highlighted in blue) path is /Volumes/config. It also doesn’t have any SASS files and is it the one that can disconnect?

glenn2223 on Apr 6, 2021

Thanks for that extra info as well. I can see you haven’t installed it. Can you take a screengrab of the “Extensions” tab?

Yours is glenn2223.live-sass (5.0.0) and it should be glenn2223.live-sass (5.0.0-rc.4.3)

glenn2223 on Apr 6, 2021