Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When using Live Share updates are not seen
See original GitHub issueWhen someone on live share edits a sass file it does not seem to get picked up as a changed file, I have to go into the file and save it myself to get it to trigger.
The other person also has the extension installed and gets the following error on their side:
Compilation Error
Error: src/client/css/base.sass: no such file or directory
Edit: if I stay in the sass file with him he is able to save from his side and it will pick up on the changes and recompile. I tried keeping the file open in a split view tab but that does not seem to work.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The extension is set up so that when you save a file it checks if that file is a Sass file and then compiles it. As you are not directly saving the file vscode doesn’t know it needs to trigger my extension.
With you having the file open directly it may apply the change as a save to keep your system up to date with the latest edit/revision.
The other user may be getting the error as the files are not local. Though I’m not sure.
I will check the live share code and see how it works. I’ll also check see if the expected behaviour is even possible in this scenario.
Please be aware that this might not even be possible
Closing as awaiting feedback