Unhandled error when path is not found - (Renamed from command fail)
See original GitHub issueAfter 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
Issue Analytics
- State:
- Created 2 years ago
- Comments:37 (15 by maintainers)
Top Results From Across the Web
11 Ways to Fix "The System Cannot Find The Path Specified ...
1. Run Command Prompt as an Administrator ... Windows utilities cannot access all files and folders available on your device. Administrative ...
Read more >func command failing due to unhandled error on VSCode
I tried removing C:\Users\<UserName>\AppData\Roaming\npm\node_modules\azure-functions-core-tools and reinstalling, but the error is bellow. < ...
Read more >"The directory name is invalid" error message when you start ...
The command prompt program or Notepad logs an error that states that the %HOMEDRIVE%%HOMEPATH% path is not valid for the session. This scenario...
Read more >Debugging errors - dbt Developer Hub
To fix this: Open the offending file (e.g. schema.yml ); Check the line in the error message (e.g. line 5 ); Find the...
Read more >file — CMake 3.25.1 Documentation
If <linkname> does not exist or is not a symlink, CMake issues a fatal error. Note that this command returns the raw symlink...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Good, I’m glad it works. v5 here we come 🎉
Thanks for your help in debugging this.
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)