-
-
Notifications
You must be signed in to change notification settings - Fork 430
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
Error: sass-loader
requires node-sass
>=4 but node-sass is already at v4
#563
Comments
@sundowndev |
Of course the folders exist. |
@sundowndev looks like you don't have |
I have it. Here is his package.json :
|
@sundowndev |
EDIT: not related with the original issue, fix below getting this error at npm install
log:
|
@sundowndev looks like a bug in |
Fixed with npm/npm#19989 but I get the same error on node-sass :
I'm on npm |
Fixed by deleting node_modules, packages-lock.json, clear cache and reinstalling each package one by one on npm 5.6.0. That's weird |
I had the exact same problem. It was because of a cached version of node-sass. This solution worked for me:
|
I've also got the same error when upgrading node from v6.12 to v8.11.1 (now npm v5.6.0): This worked for me: |
I got this consistently even after clearing out node_modules and yarn's cache. Upgraded from node 6.13.1 to 8.11.1, did |
On newer version of npm you can probably fix this with |
This is going to be a popular topic with Angular 6 now requiring node 8. |
The soluctions... All time is fails!
The versions
|
I fixed it by downgrading node from 10.0.0 to 8.9.4 nvm install 8.9.4
nvm use 8.9.4
# set v8.9.4 as the default version
nvm alias default 8.9.4 |
The same here, node 8.11.2 and nothing helps. I've tried to clear cache and upgrade all packages and still nothing. |
Having exactly the same issue here |
I was getting this issue, so I added some debug logging to sass-loader. For me the problem was the following code:
I got the following errors...
So for me... I just upgraded node to v8 and I was good. |
@sundowndev reopen the issue please, this is a real issue
|
after downgrading to
Seems like my issue was to run for information, to solve this, I edit my docker-compose.yaml file from
to
this makes the containerized app using its own |
|
Reopening the issue until it gets fixed. Quick fix solutions (just choose one of these) :
@evilebottnawi please add proper labels |
I think that the principal issue here is that
when Whereas
(see #563 (comment) for full output) |
Some node dependencies, such as `node-sass`, are platform-specific - mounting `node_modules` leads to the Docker build using missing the correct platform dependencies. See webpack-contrib/sass-loader#563 (comment)
Feel free to send a PR with showing original errors. |
Had to add |
The point is, on any previous error during installation, even if install successful afterwards on retype, sass-node will fail. If occurs any, remove node_modules and run npm install from scratch instead of just fix the command and rerun. |
Stop posting spam, just add |
|
I'm having this same issue...which I was able to fix locally, but is there a workaround for this issue from a build server? |
I moved back to very old npm 3.10.10 that has been in our build for a while and it works like a charm. |
|
This issue came after I had upgraded my Node version from v6.10.2 to v8.11.2. |
PR welcome to fix issue around error message |
ran
encore dev --watch
get this error :
but node-sass is at v4.8.3 in package.json :
already tried deleting node-modules folder and package-lock.json
The text was updated successfully, but these errors were encountered: