-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
node-sass v5.0.0 compilation error #9986
Comments
It might be a good time to move to sass (dart implementation) instead of libsass/node-sass. |
Further to the above, also note that node-sass has been deprecated. I followed this suggestion and simply replaced
|
how i resolve this issues :
|
Does this essentially mean that CRA doesn't support node 15? |
Be careful with that approach #10045 |
This Error Solved By All Possible Solution In This Article At Here Error: Node Sass version 5.0.0 is incompatible with ^4.0.0 |
Install node-sass: yarn add node-sass if not work |
Type the following command:
I hope its works. |
npm add node-sass --force works good :D 😃 |
Describe the bug
Installing
node-sass
as recommended in the documentation to have SASS support returns following error on compilation:Error: Node Sass version 5.0.0 is incompatible with ^4.0.0
sass-loader
was updated tov10.0.5
for supportingnode-sass v5.0.0
(webpack-contrib/sass-loader#899), but react-scripts is pinned tosass-loader 8.0.0
. This means that every fresh installation (or update) which is using node-sass will end up with this error onyarn/npm start
.Related issue threads:
https://stackoverflow.com/a/64626556/6402990
webpack-contrib/sass-loader#898
Did you try recovering your dependencies?
Not applicable
Which terms did you search for in User Guide?
Not applicable
Environment
All
Steps to reproduce
npx create-react-app sass-error-compilation
App.css
toApp.scss
. Change extension in App.js as well.Expected behavior
Scss files compiled to css without sass-loader returning an error.
Actual behavior
Reproducible demo
The text was updated successfully, but these errors were encountered: