-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change files throw error status 3 #22
Comments
I definitely see an issue of mixing the file paths, some parts are using forward slashes, other are using backslashes... Are you on windows running docker or virtual box or something? |
Sorry, I find this is an editor's problem, but why I don't know。 like node-sass-chokidar/issues/14 I used VSCode, and I used node-sass-chokidar's watch to do the same after the last few days. I don't know what happened, so I use atom now. Because of the problem of ability, there is no quick elimination of the problem, delay your time. |
I've created a PR that fix this problem: sass/node-sass#2386 If want to try this fix, you can patch your node-sass local copy by replacing 'node_modules/node-sass/lib/render.js' with this version: https://github.com/marcosbozzani/node-sass/blob/bug-vscode-watch/lib/render.js The diff is here: marcosbozzani/node-sass@266861b#diff-a485abf5b8f49de7f313d7799df3faf4 |
@marcosbozzani that works, awesome! |
A ready to use patch of my fix is available here: https://github.com/marcosbozzani/patch-node-sass-watch |
first save modified file, throw error, again save file, that ok
😓
The text was updated successfully, but these errors were encountered: