Can't upgrade React-Native project due dependencies - react-native

I am trying to update my RN project from 0.62.2 to the latest one (currently 0.63.3).
I am just running npm update and get errors:
npm ERR! Found: react#17.0.1
npm ERR! node_modules/react
npm ERR! react#"^17.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"16.13.1" from react-native#0.63.3
npm ERR! node_modules/react-native
npm ERR! react-native#"^0.63.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Before running npm update I had ran npx npm-check-updates -u and got the following:
#react-native-community/netinfo ^5.9.5 → ^5.9.9
#react-navigation/drawer ^5.8.6 → ^5.11.4
#react-navigation/native ^5.7.1 → ^5.8.10
#react-navigation/stack ^5.7.1 → ^5.12.8
#types/react ^16.9.43 → ^17.0.0
amazon-cognito-identity-js ^3.3.3 → ^4.5.5
aws-amplify ^3.0.21 → ^3.3.10
axios ^0.19.2 → ^0.21.0
graphql ^0.11.7 → ^15.4.0
graphql-tag ^2.10.4 → ^2.11.0
moment-timezone ^0.5.31 → ^0.5.32
react ^16.11.0 → ^17.0.1
react-native ^0.62.2 → ^0.63.3
react-native-base64 0.0.2 → 0.1.0
react-native-gesture-handler ~1.5.0 → ~1.9.0
react-native-reanimated ~1.4.0 → ~1.13.2
react-native-safe-area-context ^0.7.3 → ^3.1.9
react-native-screens 2.0.0-alpha.12 → 2.15.0
react-native-simple-crypto ^0.2.13 → ^0.2.15
react-native-vector-icons ^6.7.0 → ^7.1.0
react-navigation ^4.4.0 → ^4.4.3
#babel/core 7.8.7 → 7.12.9
#babel/runtime 7.8.7 → 7.12.5
babel-jest 24.9.0 → 26.6.3
metro-react-native-babel-preset 0.56.4 → 0.64.0
react-test-renderer 16.9.0 → 17.0.1
OK, I summarise from the error that react#^17.0.1 is wrong for react-native#0.63.3 which requires react#16.13.1 but this was produced by npx npm-check-updates -u - why it makes incompatible deps tree?..
If I change manually react version to "^16.0.0", npm install fails with:
npm ERR! Found: react#16.14.0
npm ERR! node_modules/react
npm ERR! react#"^16.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"16.13.1" from react-native#0.63.3
npm ERR! node_modules/react-native
npm ERR! react-native#"^0.63.3" from the root project
Why "react#16.14.0"?! From where?
I just can't understand how all this s..tuff works.. Please, suggest.
My current package.json:
{
"name": "Proj",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest"
},
"dependencies": {
"#react-native-community/masked-view": "^0.1.10",
"#react-native-community/netinfo": "^5.9.9",
"#react-navigation/drawer": "^5.11.4",
"#react-navigation/native": "^5.8.10",
"#react-navigation/stack": "^5.12.8",
"#types/react": "^17.0.0",
"amazon-cognito-identity-js": "^4.5.5",
"aws-amplify": "^3.3.10",
"axios": "^0.21.0",
"graphql": "^15.4.0",
"graphql-tag": "^2.11.0",
"i18n-js": "^3.8.0",
"moment-timezone": "^0.5.32",
"react": "^16.0.0",
"react-native": "^0.63.3",
"react-native-avatar-social": "0.0.3",
"react-native-base64": "0.1.0",
"react-native-gesture-handler": "~1.9.0",
"react-native-linear-gradient": "^2.5.6",
"react-native-localize": "^2.0.1",
"react-native-reanimated": "~1.13.2",
"react-native-safe-area-context": "^3.1.9",
"react-native-screens": "2.15.0",
"react-native-simple-crypto": "^0.2.15",
"react-native-tab-view": "^2.15.2",
"react-native-tab-view-viewpager-adapter": "^1.1.0",
"react-native-uuid-generator": "^6.1.1",
"react-native-vector-icons": "^7.1.0",
"react-native-video": "^4.4.5",
"react-native-viewpager": "^0.2.13",
"react-native-zeroconf": "github:atlascoder/react-native-zeroconf",
"react-navigation": "^4.4.3",
"rn-fetch-blob": "^0.12.0"
},
"devDependencies": {
"#babel/core": "7.12.9",
"#babel/runtime": "7.12.5",
"babel-jest": "26.6.3",
"metro-react-native-babel-preset": "0.64.0",
"react-test-renderer": "17.0.1"
},
"rnpm": {
"assets": [
"./assets/fonts/"
]
}
}
UPDATE
Following #anthony-marino suggestion I made manual dependencies update by update helper, and the I returned to the issue that moved my to upgrade!!
npm ERR! Found: react#16.13.1
npm ERR! node_modules/react
npm ERR! react#"16.13.1" from the root project
npm ERR! peer react#"^16.0" from #react-native-community/viewpager#4.2.1
npm ERR! node_modules/#react-native-community/viewpager
npm ERR! peer #react-native-community/viewpager#"*" from react-native-tab-view-viewpager-adapter#1.1.0
npm ERR! node_modules/react-native-tab-view-viewpager-adapter
npm ERR! react-native-tab-view-viewpager-adapter#"^1.1.0" from the root project
npm ERR! 15 more (#react-navigation/core, #react-navigation/drawer, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"16.11.0" from react-native-zeroconf#0.12.3
npm ERR! node_modules/react-native-zeroconf
npm ERR! react-native-zeroconf#"github:atlascoder/react-native-zeroconf" from the root project
npm ERR!
And the thing that runs me out..
I have a component from #react-native-community/viewpager and why if it requires peerDep react#"^16.0" - why it doesn't accept react#16.13.1. The ^16.0 means all fresher that 16.*, doesn't it?! When I check ^16.0 on npm semver calculator - it shows me 16.13.1 as suitable..
WORKAROUND
On trapping to this trouble while update:
Delete node_modules and package-lock.json
npm i
When npm i fails - remove failing dependencies
After completion of npm i - manually install removed dependencies

From your logs: react-native 0.63.3 needs react#"16.13.1", but found react#"^17.0.1". Just downgrade your react via npm install react#16.13.1 and try npm install again. It should work without errors. If you run npm outdated you'll see that "react" is outdated. But it's unlikely that you're going to have all your packages in the latest version.

so I've also run into this problem when I migrated from RN 0.63.1 to 0.64.1 so I solved it in this way:
Step run npx react-native upgrade for me it updated react and react-native
Then I've updated these dependencies mannually:
"#babel/core": "^7.12.9",
"#babel/runtime": "^7.12.5",
"#react-native-community/eslint-config": "^2.0.0",
"babel-jest": "^26.6.3",
"eslint": "7.14.0",
"jest": "^26.6.3",
"metro-react-native-babel-preset": "^0.64.0",
"react-test-renderer": "17.0.1"
you could use this tool to see what changes did these command npx react-native upgrade and what changes you have to do it manualy
https://react-native-community.github.io/upgrade-helper/?from=0.63.1&to=0.64.1
Then run npm install --force to update package-lock.json with new dependency that you've added manually.
If you have tests with Jest probably then you have to adjust a few things as well go to jest.configs.js and make sure you have here react-native and #react-native as well
transformIgnorePatterns: [
'node_modules/(?!(jest-)?react-native|#react-native|#react-native-community)',
],
and probably you'll have some problem with these mock as well
// The old way
jest.mock('react-native/Libraries/Animated/src/NativeAnimatedHelper');
// Here path was updated
jest.mock('react-native/Libraries/Animated/NativeAnimatedHelper');
Now you should be good to go, this example was for upgrading RN from 0.63.1 to 0.64.1 but it could work for you as well.
p.s I'm using node -v 14.15.4 and npm -v 7.7.6 you may have less problem if you're using npm v6

This solved my problem.
npm install #react-native-community/masked-view --force

I had to use :
npm i --legacy-peer-deps

Related

How to read ERESOLVE in npm audit fix?

Here is the output I have after getting audit warnings after installing an npm package:
$ npm audit fix
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: eslint-config-standard-with-typescript#21.0.1
npm ERR! Found: #typescript-eslint/eslint-plugin#5.46.1
npm ERR! node_modules/#typescript-eslint/eslint-plugin
npm ERR! dev #typescript-eslint/eslint-plugin#"^5.46.1" from the root project
npm ERR! peerOptional #typescript-eslint/eslint-plugin#"^5.0.0" from eslint-plugin-unused-imports#2.0.0
npm ERR! node_modules/eslint-plugin-unused-imports
npm ERR! dev eslint-plugin-unused-imports#"^2.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer #typescript-eslint/eslint-plugin#"^4.0.1" from eslint-config-standard-with-typescript#21.0.1
npm ERR! node_modules/eslint-config-standard-with-typescript
npm ERR! dev eslint-config-standard-with-typescript#"^21.0.1" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: #typescript-eslint/eslint-plugin#4.33.0
npm ERR! node_modules/#typescript-eslint/eslint-plugin
npm ERR! peer #typescript-eslint/eslint-plugin#"^4.0.1" from eslint-config-standard-with-typescript#21.0.1
npm ERR! node_modules/eslint-config-standard-with-typescript
npm ERR! dev eslint-config-standard-with-typescript#"^21.0.1" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/lancepollard/.npm/_logs/2023-01-02T17_19_47_490Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/lancepollard/.npm/_logs/2023-01-02T17_19_47_490Z-debug-0.log
That came after running npm audit fix --force a few times, after getting this:
$ npm install eslint-plugin-unused-imports --save-dev
added 2 packages, and audited 379 packages in 4s
107 packages are looking for funding
run `npm fund` for details
5 high severity vulnerabilities
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
Any ideas what I should be doing here to resolve and get a successful install?
My package.json is:
{
"main": "./host",
"type": "module",
"scripts": {
"build": "tsc && tsc-alias",
"watch": "concurrently --kill-others \"tsc -w\" \"tsc-alias -w\"",
"lint": "eslint --ext .ts ./make",
"lint:fix": "npm run lint -- --fix",
"test": "node host/task/build"
},
"devDependencies": {
"#trivago/prettier-plugin-sort-imports": "^4.0.0",
"#types/glob": "^8.0.0",
"#types/lodash": "^4.14.191",
"#types/node": "^18.11.17",
"#typescript-eslint/eslint-plugin": "^5.46.1",
"#typescript-eslint/parser": "^5.46.1",
"concurrently": "^7.6.0",
"eslint": "^8.30.0",
"eslint-config-prettier": "^8.5.0",
"eslint-config-standard-with-typescript": "^21.0.1",
"eslint-import-resolver-typescript": "^3.5.2",
"eslint-plugin-import": "^2.24.1",
"eslint-plugin-n": "^15.6.0",
"eslint-plugin-prettier": "^4.2.1",
"eslint-plugin-promise": "^6.1.1",
"eslint-plugin-simple-import-sort": "^8.0.0",
"eslint-plugin-sort-exports": "^0.8.0",
"eslint-plugin-sort-keys": "^2.3.5",
"eslint-plugin-typescript-sort-keys": "^2.1.0",
"eslint-plugin-unused-imports": "^2.0.0",
"prettier": "2.8.1",
"ts-node": "^10.9.1",
"tsc-alias": "^1.8.2",
"typescript": "^4.9.4"
},
"dependencies": {
"#lancejpollard/pretty-compact-json.js": "^0.2.0",
"chalk": "^5.2.0",
"glob": "^8.0.3",
"lodash": "^4.17.21",
"source-map": "^0.7.4"
}
}
Now I have rm -rf node_modules, and when I do npm install again, it shows the same error....
I had the same problem. Deleting the package-lock.json and the node_modules, and then running npm install solved my issue.
I hope it helps.

Version mismatch vite and quasar

Trying to install Quasar on my Vite (Vue 3) project. Getting the following error:
$ npm install -D #quasar/vite-plugin#latest sass#1.32.12
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: diop-dash#0.0.0
npm ERR! Found: #vitejs/plugin-vue#4.0.0
npm ERR! node_modules/#vitejs/plugin-vue
npm ERR! dev #vitejs/plugin-vue#"^4.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer #vitejs/plugin-vue#"^2.0.0 || ^3.0.0" from #quasar/vite-plugin#1.2.3
npm ERR! node_modules/#quasar/vite-plugin
npm ERR! dev #quasar/vite-plugin#"1.2.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
From this it looks like quasar's vite plugin is looking for the 2.0.0 or 3.0.0 version of #vitejs/plugin-vue but I have 4.0 installed. Is quasar not compatible with the new one, will I run into trouble if I use the --force flag? Is there another way to resolve this that doesn't involve downgrading my Vite setup?
From package.json
"dependencies": {
"#quasar/extras": "^1.15.8",
"pinia": "^2.0.28",
"quasar": "^2.10.2",
"vue": "^3.2.45",
"vue-router": "^4.1.6"
},
"devDependencies": {
"#quasar/vite-plugin": "^1.2.3",
"#rushstack/eslint-patch": "^1.1.4",
"#types/node": "^18.11.12",
"#vitejs/plugin-vue": "^4.0.0",
"#vue/eslint-config-prettier": "^7.0.0",
"#vue/eslint-config-typescript": "^11.0.0",
"#vue/tsconfig": "^0.1.3",
"eslint": "^8.22.0",
"eslint-plugin-vue": "^9.3.0",
"npm-run-all": "^4.1.5",
"prettier": "^2.7.1",
"sass": "^1.32.12",
"typescript": "~4.7.4",
"vite": "^4.0.0",
"vue-tsc": "^1.0.12"
}

Can't use npm install after I updated the version of all nestjs dependencies in my package.json

I have created a new nestjs project and installed several additional standard packages. In the console it said that the packages are outdated and there are 7 red vulnerabilities.
The suggested command npm audit fix --force did't help - there were still 4 red vulnerabilities after that.
I found a command that updates my packages to the latest versions:
npm install -g npm-check-updates
ncu -u
npm install
Now I can't use npm install:
npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: #nestjs/typeorm#8.0.4
npm ERR! Found: typeorm#0.3.6
npm ERR! node_modules/typeorm
npm ERR! typeorm#"^0.3.6" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer typeorm#"^0.2.34" from #nestjs/typeorm#8.0.4
npm ERR! node_modules/#nestjs/typeorm
npm ERR! #nestjs/typeorm#"^8.0.4" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: typeorm#0.2.45
npm ERR! node_modules/typeorm
npm ERR! peer typeorm#"^0.2.34" from #nestjs/typeorm#8.0.4
npm ERR! node_modules/#nestjs/typeorm
npm ERR! #nestjs/typeorm#"^8.0.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
I deleted node_modules as well as the package-lock.json and then forced the installation with npm install --force. But I get again the message about severity vulnerabilities:
npm install --force
npm WARN using --force Recommended protections disabled.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: #nestjs/typeorm#8.0.4
npm WARN Found: typeorm#0.3.6
npm WARN node_modules/typeorm
npm WARN typeorm#"^0.3.6" from the root project
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer typeorm#"^0.2.34" from #nestjs/typeorm#8.0.4
npm WARN node_modules/#nestjs/typeorm
npm WARN #nestjs/typeorm#"^8.0.4" from the root project
npm WARN
npm WARN Conflicting peer dependency: typeorm#0.2.45
npm WARN node_modules/typeorm
npm WARN peer typeorm#"^0.2.34" from #nestjs/typeorm#8.0.4
npm WARN node_modules/#nestjs/typeorm
npm WARN #nestjs/typeorm#"^8.0.4" from the root project
added 823 packages, and audited 824 packages in 29s
84 packages are looking for funding
run `npm fund` for details
7 high severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
I am going in circles and do not understand how to solve the problem. And especially which version I need to use that has no red security issues?
My package.json file now looks like this:
{
"name": "api",
"version": "0.0.1",
"description": "",
"author": "",
"private": true,
"license": "UNLICENSED",
"scripts": {
"prebuild": "rimraf dist",
"build": "nest build",
"format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"",
"start": "nest start",
"start:dev": "nest start --watch",
"start:debug": "nest start --debug --watch",
"start:prod": "node dist/main",
"lint": "eslint \"{src,apps,libs,test}/**/*.ts\" --fix",
"test": "jest",
"test:watch": "jest --watch",
"test:cov": "jest --coverage",
"test:debug": "node --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBand",
"test:e2e": "jest --config ./test/jest-e2e.json"
},
"dependencies": {
"#nestjs/common": "^8.4.5",
"#nestjs/core": "^8.4.5",
"#nestjs/platform-express": "^8.4.5",
"#nestjs/typeorm": "^8.0.4",
"class-transformer": "^0.5.1",
"class-validator": "^0.13.2",
"reflect-metadata": "^0.1.13",
"rimraf": "^3.0.2",
"rxjs": "^7.5.5",
"sqlite3": "^5.0.8",
"typeorm": "^0.3.6"
},
"devDependencies": {
"#nestjs/cli": "^8.2.6",
"#nestjs/schematics": "^8.0.11",
"#nestjs/testing": "^8.4.5",
"#types/express": "^4.17.13",
"#types/jest": "27.5.1",
"#types/node": "^17.0.35",
"#types/supertest": "^2.0.12",
"#typescript-eslint/eslint-plugin": "^5.26.0",
"#typescript-eslint/parser": "^5.26.0",
"eslint": "^8.16.0",
"eslint-config-prettier": "^8.5.0",
"eslint-plugin-prettier": "^4.0.0",
"jest": "^28.1.0",
"prettier": "^2.6.2",
"source-map-support": "^0.5.21",
"supertest": "^6.2.3",
"ts-jest": "^28.0.3",
"ts-loader": "^9.3.0",
"ts-node": "^10.8.0",
"tsconfig-paths": "^4.0.0",
"typescript": "^4.7.2"
},
"jest": {
"moduleFileExtensions": [
"js",
"json",
"ts"
],
"rootDir": "src",
"testRegex": ".*\\.spec\\.ts$",
"transform": {
"^.+\\.(t|j)s$": "ts-jest"
},
"collectCoverageFrom": [
"**/*.(t|j)s"
],
"coverageDirectory": "../coverage",
"testEnvironment": "node"
}
}
Why do I get an indication that I am using typeorm#"^0.2.34" even though my package.json file specifies a newer version "typeorm": "^0.3.6"? This is also the latest version at the moment.
PS: If I change the typorm version back to 0.2.34 or 0.2, I can use npm install again but I get the red "7 high severity vulnerabilities" message.
Same issue for me. Using npm install --legacy-peer-deps seems to fix the issue however vulnerabilities remains.
Hello I just got the some problem as yours it's because the nest and npm commands getting blocked so try to allow it from Windows PowerShell by following these steps here
update to the latest npm version by running this command
npm i -g npm#latest

vuejs 3 I deleted folder node_modules and now npm install has error

I have a work project, but I deleted folder node_modules and now npm install has error.
node v16.13.2
#vue/cli 4.5.15
my package.json
"dependencies": {
"#capacitor/android": "3.4.3",
"#capacitor/app": "1.1.0",
"#capacitor/core": "3.4.1",
"#capacitor/haptics": "1.1.4",
"#capacitor/keyboard": "1.2.2",
"#capacitor/status-bar": "1.0.8",
"#ionic/vue": "^6.0.9",
"#ionic/vue-router": "^6.0.0",
"#popperjs/core": "^2.11.2",
"axios": "^0.25.0",
"core-js": "^3.6.5",
"eslint-loader": "^4.0.2",
"vue": "^3.2.21",
"vue-axios": "^3.4.0",
"vue-router": "^4.0.12",
"vuex": "^4.0.2"
},
"devDependencies": {
"#babel/eslint-parser": "^7.17.0",
"#babel/eslint-plugin": "^7.16.5",
"#capacitor/cli": "3.4.1",
"#vue/cli-plugin-babel": "~4.5.15",
"#vue/cli-plugin-eslint": "~4.5.15",
"#vue/cli-service": "~4.5.15",
"#vue/compiler-sfc": "^3.0.0",
"eslint": "^7.0.0",
"eslint-plugin-vue": "^7.0.0"
},
npm install
# npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: dev.infi.loc#0.1.0
npm ERR! Found: eslint#7.32.0
npm ERR! node_modules/eslint
npm ERR! dev eslint#"^7.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint#">= 1.6.0 < 7.0.0" from #vue/cli-plugin-eslint#4.5.17
npm ERR! node_modules/#vue/cli-plugin-eslint
npm ERR! dev #vue/cli-plugin-eslint#"~4.5.15" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\xxx\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xxx\AppData\Local\npm-cache\_logs\2022-03-27T14_01_53_031Z-debug.log
How can I fix it? Please help. Thanks in advance.
Error screen https://i.stack.imgur.com/QmLtI.png
It happened to me a while ago, i dont know if the solutions is still going to work but, tried deleting the package.json then use npm init hen run dependency-check in your project directory followed by a npm install
A solution that worked for me was upgrading #vue/cli-plugin-eslint to ^5.0.4 (The ^ means "up to next major").
On a side note, you should keep all your packages as up-to-date as possible for security reasons.

Error installing node-sass dependency

I am trying to npm install a package.json with the following dependencies:
"devDependencies": {
"browser-sync": "^2.8.2",
"del": "^1.2.0",
"gulp": "^3.9.0",
"gulp-autoprefixer": "^2.3.1",
"gulp-babel": "^5.2.0",
"gulp-concat": "^2.6.0",
"gulp-eslint": "^1.0.0",
"gulp-filesize": "0.0.6",
"gulp-header": "^1.2.2",
"gulp-imagemin": "^2.3.0",
"gulp-jshint": "^1.11.2",
"gulp-livereload": "^3.8.0",
"gulp-minify-css": "^1.2.0",
"gulp-newer": "^0.5.1",
"gulp-notify": "^2.2.0",
"gulp-plumber": "^1.0.1",
"gulp-rename": "^1.2.2",
"gulp-sass": "^2.0.4",
"gulp-sourcemaps": "^1.5.2",
"gulp-svgmin": "^1.2.0",
"gulp-svgstore": "^5.0.4",
"gulp-uglify": "^1.2.0",
"imagemin-pngquant": "^4.1.2"
},
"dependencies": {
"node-sass": "^3.2.0"
}
But it fails with the node-sass package.
A part of the output is this:
Cannot download "https://github.com/sass/node-sass/releases/download/v3.2.0/darwin-x64-51_binding.node": HTTP error 404 Not Found
And then:
node-sass#3.2.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#3.2.0 postinstall script 'node scripts/build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
Node version 7.5.0 and npm version 4.1.2, OSX Sierra
Any suggestions?
I had same issue using node 8.1.3. I solved downgrading to latest long term supported version of nodejs (now is the 6.11.0).
The problem is that node-sass doesn't supports some nodejs versions....