search

armin-pfaeffle / sass-autocompile

Automatically compiles SASS files on save ‒ package for atom.io
https://atom.io/packages/sass-autocompile
MIT License
49 stars 16 forks source link

File to read not found or unreadable #165

Open EB-DA opened 5 years ago

EB-DA commented 5 years ago

Hi, I have to make two premises: 1) I'm a bit lost on the programming side, so don't take much knowledge for granted on my part, and 2) I had setup SASS Autocompile to work properly in my previous pc, now I'm having the issue after installing all over on a new machine.

The issue quick and simple is that, when I save my .scss file, I get "File to read not found or unreadable: path/path/path/style.scss".

Now, rewinding from the start, what did I do? 1) I installed Atom on this pc (previous one had Windows 7, this one has Windows 10) and imported settings and packages that I exported from the other pc through another package. 2) Installed SASS Autocompile package on Atom. 3) Installed node.js from the link here: https://atom.io/packages/sass-autocompile 4) Installed Ruby. 5) Through cmd prompt, installed node-sass via the command specified in the above link.

Then I opened my .scss file on Atom and tried to save/compile it (autocompile on save is enabled), but I get that error. The file is on a local server, it gets opened and saved properly from/to its location, but not compiled. I looked everywhere for solutions, but I'm not entirely sure what the error actually is and what are relevant answers for that matter.

Any help? Thanks in advance.

armin-pfaeffle commented 5 years ago

Hey! Ruby is not necessary for using my package!

Can you tell me where your file is stored?

Can you give me a screenshot of this error?

EB-DA commented 5 years ago

Hi, thanks for the reply. As a side note, I wasn't able to install node-sass without Ruby, the cmd prompt gave only errors; but regardless of that...

The files are inside a NAS server in the office. The NAS and the pc aren't directly cabled together (they weren't with the previous pc, and they aren't now); the NAS is cabled to the phone/internet plug on the wall near its position, and the pc is cabled to the one next to itself. Nothing changed in the NAS configuration, in fact another pc that was and is still connected in the same manner is still able to compile from/to the NAS location. I tried to connect the old pc again, and it still compiles normally, while this new one does not.

Here's the screenshot attachment (clicking the error brings me back to the top of the file, nothing more):

Immagine

Pathos444 commented 4 years ago

Hi,

Have you found any solution to this issue ? I'm getting the same error and can't find how to fix it. Thanks !

webmasterpf commented 4 years ago

Hi. I get the same error with this detailed output:

{
  "status": 3,
  "message": "File to read not found or unreadable: //DG-PC-ADM-09/Dev-local/lerocher_d8_2019/sass/content-type-style/_frontpage-style.scss",
  "formatted": "Internal Error: File to read not found or unreadable: //DG-PC-ADM-09/Dev-local/lerocher_d8_2019/sass/content-type-style/_frontpage-style.scss\n"
}

In VS Code, autocompile work great so node and node-sass are fonctionnal. If someone know about this. Thanks