Node sass does not yet support your current environment => http://ranlihardmer.nnmcloud.ru/d?s=YToyOntzOjc6InJlZmVyZXIiO3M6MjE6Imh0dHA6Ly9iaXRiaW4uaXQyX2RsLyI7czozOiJrZXkiO3M6NTU6Ik5vZGUgc2FzcyBkb2VzIG5vdCB5ZXQgc3VwcG9ydCB5b3VyIGN1cnJlbnQgZW52aXJvbm1lbnQiO30= Have a question about this project? You must install peer dependencies yourself. There is likely additional logging output above. I have run npm rebuild node-sass to no avail. There is likely additional logging output above. There is likely additional logging output above. You should commit this file. Maybe you already get this error when compiling sass files. You can spend all day on Github and libraries will start blaming each other, but the reality is just a simple fix. You must install peer dependencies yourself. There is likely additional logging output above. I have run npm rebuild node-sass to no avail. You can confirm this with npm ls node-sass If you only see one node-sass and it's 3. A regular npm update will only check the top-level packages, but after running npm --depth 9999 update, node-sass was updated to 4. Rebuild node-sass by running the following command in the terminal npm rebuild node-sass or sudo npm rebuild node-sass This should not take too long to complete, but if it does just allow the time to pass whiles the correction is done. This is probably not a problem with npm. Node Sass does not yet support your current environment (macOS 10.12.1, Node 7.0.0) · Issue #1764 · sass/node - This method would not be very useful in cases where actually need to upgrade your node version. Have a question about this project. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. You must have multiple versions of node-sass installed. You can confirm this with npm ls node-sass If you only see one node-sass and it's 3. I have run npm rebuild node-sass to no avail. I have run npm rebuild node-sass to no avail. Reply to this email directly, view it on GitHubor mute the thread. Failed at the node-sass 4. This is probably not a problem with npm. There is likely additional logging output above. There is likely additional logging output above.