Skip to content
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

Closed
hehehai opened this issue Oct 6, 2017 · 6 comments
Closed

change files throw error status 3 #22

hehehai opened this issue Oct 6, 2017 · 6 comments

Comments

@hehehai
Copy link

hehehai commented Oct 6, 2017

yarn run v1.1.0
$ node-sass-chokidar src/ -o src/ --watch --recursive
=> changed: G:\webDev\fullStack\node-sass-test\src\xx.scss
{
  "status": 3,
  "message": "File to read not found or unreadable: G:/webDev/fullStack/node-sass-test/src/xx.scss",
  "formatted": "Internal Error: File to read not found or unreadable: G:/webDev/fullStack/node-sass-test/src/xx.scss\n"
}
=> changed: G:\webDev\fullStack\node-sass-test\src\xx.scss
Rendering Complete, saving .css file...
Wrote CSS to G:\webDev\fullStack\node-sass-test\src\xx.css
node v8.6.0
yarn v1.1.0
"node-sass-chokidar": "^0.0.3"

first save modified file, throw error, again save file, that ok

😓

@michaelwayman
Copy link
Owner

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?

@hehehai
Copy link
Author

hehehai commented Oct 9, 2017

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'm sorry!

@hehehai hehehai closed this as completed Oct 11, 2017
@xxDukeMCxx
Copy link

Hi,

Have the same problem with VSCODE.
Read a lot of issues here and there about the fact that Chokidar detect the file change before VSCODE unlock it. Not a expert at all, but find that add the "--usePolling" param can help with VSCODE (error still raise, but a lot less).
Exemple :
image

@marcosbozzani
Copy link

marcosbozzani commented May 18, 2018

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

@yusriyunus
Copy link

@marcosbozzani that works, awesome!

@marcosbozzani
Copy link

A ready to use patch of my fix is available here: https://github.com/marcosbozzani/patch-node-sass-watch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants