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

I am not able to run SASS #2531

Closed
gfdesign opened this issue Jun 14, 2017 · 6 comments
Closed

I am not able to run SASS #2531

gfdesign opened this issue Jun 14, 2017 · 6 comments

Comments

@gfdesign
Copy link

gfdesign commented Jun 14, 2017

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

@Timer
Copy link
Contributor

Timer commented Jun 14, 2017

/cc @michaelwayman

@michaelwayman
Copy link
Contributor

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

@michaelwayman
Copy link
Contributor

@gfdesign I tried duplicating your problem on a windows10 laptop with npm6/node3.10.10 and I wasn't able to duplicate the issue.

Question time:
do you have some sort of mounted file system or running a VM or windows/linux hybrid? Are you running cygwin or have symlinks or anything like that?

The BEST would be if you could share a small project that demonstrates the issue. But otherwise is it possible for you to include your package.json, and example of your sass folder/file structure so I can try replicating your setup even further?

@gfdesign
Copy link
Author

Thanks for replying. As soon as I find some time, I'll try your suggestions.
Thanks for your patience.

@gfdesign
Copy link
Author

This thread is followed here.

@gaearon
Copy link
Contributor

gaearon commented Oct 2, 2018

Sass is now supported out of the box.
https://reactjs.org/blog/2018/10/01/create-react-app-v2.html

@lock lock bot locked and limited conversation to collaborators Jan 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants