I'm struggling with installing the gh-pages npm.
Here are the errors I got:
npm WARN deprecated fsevents#1.2.4: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
added 12 packages, and audited 1974 packages in 11s
97 packages are looking for funding
run `npm fund` for details
81 vulnerabilities (14 low, 20 moderate, 42 high, 5 critical)
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.
Can somebody help me with this, please?
I tried
npm install gh-pages --save-dev
"dependencies": {
"#testing-library/jest-dom": "^5.16.5",
"#testing-library/react": "^13.4.0",
"#testing-library/user-event": "^13.5.0",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-scripts": "^2.1.3",
"web-vitals": "^2.1.4"
}
"devDependencies": {
"gh-pages": "^4.0.0",
"github-pages": "^3.0.2"
}
Related
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
I have been starting my story with React Native (Expo). Someday I needed to install datetimepicker. Unfortunately, I have done something wrong. I tried to face the problem by myself. I removed the node_modeles directory and package.lock.json. When I trying to npm install I get the error below:
error message
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined#undefined
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.8.3" from #react-native-community/datetimepicker#3.4.6
npm ERR! node_modules/#react-native-community/datetimepicker
npm ERR! #react-native-community/datetimepicker#"^3.0.4" from the root project
npm ERR! 1 more (react-native)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"17.0.1" from react-native-windows#0.64.3
npm ERR! node_modules/react-native-windows
npm ERR! peer react-native-windows#">=0.62" from #react-native-community/datetimepicker#3.4.6
npm ERR! node_modules/#react-native-community/datetimepicker
npm ERR! #react-native-community/datetimepicker#"^3.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 know that is something with the wrong versions of dependencies but I have no idea how to fixed it :(
That is my package.json.
UPDATED package.json
{
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web",
"eject": "expo eject"
},
"dependencies": {
"#react-native-async-storage/async-storage": "^1.13.0",
"#react-native-picker/picker": "1.9.11",
"#react-navigation/bottom-tabs": "^5.11.10",
"#react-navigation/drawer": "^5.12.5",
"#react-navigation/native": "^5.9.4",
"#react-navigation/stack": "^5.14.4",
"#types/expo__vector-icons": "^9.0.1",
"expo": "~41.0.0",
"expo-app-loading": "^1.0.3",
"expo-notifications": "~0.11.5",
"expo-sms": "~9.1.2",
"expo-status-bar": "~1.0.4",
"i18n-js": "^3.8.0",
"moment": "^2.29.1",
"react": "16.13.1",
"react-dom": "16.13.1",
"react-native": "https://github.com/expo/react-native/archive/sdk-41.0.0.tar.gz",
"react-native-gesture-handler": "~1.10.2",
"react-native-pager-view": "5.0.12",
"react-native-reanimated": "~1.13.0",
"react-native-safe-area-context": "3.2.0",
"react-native-screens": "~3.0.0",
"react-native-tab-view": "^3.0.1",
"react-native-web": "^0.13.18",
"react-native-webview": "11.2.3",
"react-navigation-header-buttons": "^7.0.1",
"react-redux": "^7.2.3",
"redux": "^4.0.5",
"redux-thunk": "^2.3.0"
},
"devDependencies": {
"#babel/core": "~7.9.0",
"#types/i18n-js": "^3.8.0",
"#types/react": "~16.9.35",
"#types/react-dom": "^17.0.3",
"#types/react-native": "~0.63.2",
"#types/react-redux": "^7.1.16",
"typescript": "~4.0.0"
},
"private": true
}
How can I make it working again?
UPDATE #1
I have created a new project and I have installed all dependencies by expo install without react-native-modal-datetime-picker. I have copied and dependencies to my original project. When I used npm install my project installed correctly with the message:
22:39 $ npm install
npm WARN deprecated deep-assign#3.0.0: Check out `lodash.merge` or `merge-options` instead.
npm WARN deprecated #hapi/topo#3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated #hapi/bourne#1.3.2: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated #hapi/address#2.1.4: Moved to 'npm install #sideway/address'
npm WARN deprecated #hapi/hoek#8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated uglify-es#3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated #hapi/joi#15.1.1: Switch to 'npm install joi'
npm WARN deprecated core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated core-js#2.6.12: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated core-js#2.6.12: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated core-js#2.6.12: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated core-js#2.6.12: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm WARN deprecated core-js#2.6.12: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
added 1087 packages, and audited 1088 packages in 30s
60 packages are looking for funding
run `npm fund` for details
12 low severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
Right now I'm trying to install react-native-modal-datetime-picker (https://github.com/mmazzarolo/react-native-modal-datetime-picker) and I'm getting error:
22:44 $ expo install react-native-modal-datetime-picker #react-native-community/datetimepicker
Installing 1 SDK 41.0.0 compatible native module and 1 other package using npm.
> npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined#undefined
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.8.3" from #react-native-community/datetimepicker#3.2.0
npm ERR! node_modules/#react-native-community/datetimepicker
npm ERR! #react-native-community/datetimepicker#"3.2.0" from the root project
npm ERR! 1 more (react-native)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"17.0.1" from react-native-windows#0.64.3
npm ERR! node_modules/react-native-windows
npm ERR! peer react-native-windows#">=0.62" from #react-native-community/datetimepicker#3.2.0
npm ERR! node_modules/#react-native-community/datetimepicker
npm ERR! #react-native-community/datetimepicker#"3.2.0" 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 /home/adas/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/adas/.npm/_logs/2021-04-17T20_53_05_643Z-debug.log
npm exited with non-zero code: 1
Error: npm exited with non-zero code: 1
at ChildProcess.completionListener (/home/adas/.nvm/versions/node/v14.16.0/lib/node_modules/expo-cli/node_modules/#expo/spawn-async/src/spawnAsync.ts:65:13)
at Object.onceWrapper (events.js:422:26)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.EventEmitter.emit (domain.js:467:12)
at maybeClose (internal/child_process.js:1048:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
...
at Object.spawnAsync [as default] (/home/adas/.nvm/versions/node/v14.16.0/lib/node_modules/expo-cli/node_modules/#expo/spawn-async/src/spawnAsync.ts:26:19)
at NpmPackageManager._runAsync (/home/adas/.nvm/versions/node/v14.16.0/lib/node_modules/expo-cli/node_modules/#expo/package-manager/src/NodePackageManagers.ts:166:31)
at NpmPackageManager.addAsync (/home/adas/.nvm/versions/node/v14.16.0/lib/node_modules/expo-cli/node_modules/#expo/package-manager/src/NodePackageManagers.ts:105:18)
at installAsync (/home/adas/.nvm/versions/node/v14.16.0/lib/node_modules/expo-cli/src/commands/install.ts:130:3)
at Command.<anonymous> (/home/adas/.nvm/versions/node/v14.16.0/lib/node_modules/expo-cli/src/exp.ts:349:7)
Try Updating packages to the latest version.
npm update
give a try to install with --force flag as well if the update has not worked. eg:
npm install --force
try running this:
npm install --legacy-peer-deps --global expo-cli
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
npm i -D webpack
gives me the
npm ERR! Maximum call stack size exceeded
do i need to run the below command to install webpack
npm install --no-optional webpack --save-dev
why i am not able to install webpack with npm i webpack ?
i am using below versions
node - 8.11.1
npm -5.6.0
package.json
"dependencies": {
"react": "^16.5.2",
"react-dom": "^16.5.2"
},
"devDependencies": {
"babel": "^6.23.0",
"babel-core": "^6.26.3",
"babel-loader": "^8.0.4",
"babel-preset-env": "^1.7.0",
"babel-preset-react": "^6.24.1",
"html-webpack-plugin": "^3.2.0",
"http-server": "^0.11.1",
"webpack-cli": "^3.1.2",
"webpack-dev-server": "^3.1.9"
}
I would recommend the installation process as described on the webpack website
npm install --save-dev webpack
Or if you want a specific version
npm install --save-dev webpack#<version>
Note: If your using webpack v4 or later you also need to install the CLI
npm install --save-dev webpack-cli
If --save-dev argument doesn't work try deleting package-lock.json and retry
If you're still experiencing problems, here's a link to a GitHub issue with more solutions
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....