question-mark
Stuck on an issue?

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.

I am not able to run SASS

See original GitHub issue

Dears I am try to run SASS in my React app following these instructions. When I run npm run watch-css the script generates correctly the .css from the .scss file, however when I save the .scss file I get this message in the console:

=> changed: C:\React\MyApp\src\App.scss
{
  "status": 3,
  "message": "File to read not found or unreadable: C:/React/MyApp/src/App.scss",
  "formatted": "Internal Error: File to read not found or unreadable: C:/React/MyApp/src/App.scss\n"
}

My enviroment and setup are: Windows 10 Node: 6.10.2 NPM: 3.10.10 react: 15.6.0 react-dom: 15.6.0 node-sass-chokidar: 0.0.3, react-scripts: 1.0.7

Any idea what is wrong? I would be grateful any clue. Best regards

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
michaelwaymancommented, Jun 14, 2017

Thanks for the heads-up @Timer @gfdesign would you mind re-opening the ticket on node-sass-chokidar so I will be able to track it better?

At first glance it looks like you are on windows and node-sass-chokidar is trying to look for file C:/React/MyApp/src/App.scss (note the forward slashes) but on windows the correct path would use \ backslashes instead.

I released node-sass-chokidar v0.0.3 yesterday and I am wondering if this new “patch” release introduced a bug on accident. Would you mind downgrading to node-sass-chokidar v0.0.2 and see if this is still an issue for you? That gives a chance to tell me exactly where the issue is at.

There are no hard-coded forward slashes in the code, and I am confident node knows how to properly resolve paths so I am thinking this might be an issue with a dependency node-sass-chokidar has on sass-graph.

I will look into this issue more in-depth when I get home from work, in the meantime if you could re-open this issue on node-sass-chokidar and let me know if downgrading fixes your issue that would be a major help!

Thanks for the report @gfdesign

0reactions
gaearoncommented, Oct 2, 2018
Read more comments on GitHub >

github_iconTop Results From Across the Web

Install Sass
First install Sass using one of the options below, then run sass --version to be sure it installed correctly. If it did, this...
Read more >
Why I can't run “npm run sass”? - Stack Overflow
Install node-sass by running npm i node-sass in your terminal. You should be able to run the other after doing that.
Read more >
How to run Sass in the Command Line | by Laura-Louise Tobin
Once you have your Sass files written, you're ready to go! The command to run Sass is sass --watch input.scss output.css where 'input.scss'...
Read more >
How to start using Sass without having to worry ... - YouTube
Sass is awesome, but if you aren't familiar with command line tools like npm, it can be a pain to have to learn...
Read more >
Sass Compiler NOT Working in Visual Studio Code - YouTube
In this tutorial I am going to explain how to fix the visual studio code live sass compiler extension if it is not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found