-
-
Notifications
You must be signed in to change notification settings - Fork 27k
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
SASS and SourceMap woes #4381
Comments
Are you comfortable testing the v2 beta? It has native support for Sass. 😄
|
Hi, Installed with Github issues all over the place in terms of clear instructions, with many issues claiming it's not working, not to mention support for source maps. Got to a point where I think I have every thing is set up, but it refuses to read my scss files with |
Closing because v2 has Sass support. |
Still same issue for v2 |
The issue is still persisted with 2.0.4 (both CSS and SASS). Please consider to re-open this. |
I upgraded react-scripts to the latest, added node-sass as a dependency, and to get sourcemaps working, I had to add
|
@orszaczky i tried your solution but didn't work
the issue is source-maps doesn't show in development or "yarn start" which is crucial |
@mostafaabobakr7 This is my full config, hope it helps. I'm not using yarn, but it works for me with npm.
|
Could you please tell me what is wrong with my approach to get your solution to work ? |
GUYS |
Is this a bug report?
No
Problem
I've given this a fair amount of time but I simply cannot got to any elegant solution if any. I've setup my project to use SASS and
node-sass-chokidar
to read and compile the sass into my src directory.When using
import './App.css';
there is no way to inspect elements and get their location in SASS due to the inlining and no reference to the map file. Element locations only read as<style></style>
in the inspector.Any option to put the css and map file into the public folder creates a full reload and makes the development process with css even more painful.
I feel i might be missing something here, because the default configuration is simply not an efficient way to write and maintain SASS, along with keeping all the hot reloading tech in place.
Any help would be much appreciated.
Thanks
The text was updated successfully, but these errors were encountered: