Related
I built an admin dashboard with Creative Tim's argon-dashboard-pro-nodejs template about two years ago.
They no longer maintain this template and they haven't updated it in about 4 years. I haven't touched my app in the last two years.
I recently got a new computer and wanted to update and make changes to the app but it won't even start on my local machine.
I ran npm install to install all dependencies (that's the first thing I'm supposed to do right?)
Then ran npm run dev, I get this error:
> argon-dashboard-pro-nodejs#1.0.1 dev
> concurrently "pm2 start" "gulp"
sh: concurrently: command not found
Even though my package.json lists concurrently and looks like this:
{
"name": "argon-dashboard-pro-nodejs",
"version": "1.0.1",
"private": true,
"scripts": {
"pm2": "pm2",
"gulp": "gulp",
"start": "node ./bin/www",
"start:staging": "pm2 start",
"dev": "concurrently \"pm2 start\" \"gulp\"",
"monitor": "pm2 monit",
"reload-env": "pm2 reload --update-env ecosystem.config.js",
"stop": "pm2 stop ecosystem.config.js",
"delete": "pm2 delete ecosystem.config.js",
"knex": "knex --knexfile ./db/knexfile.js --debug"
},
"dependencies": {
"#babel/core": "^7.10.5",
"#babel/preset-env": "^7.10.4",
"#google-cloud/firestore": "^3.8.6",
"#google-cloud/storage": "^4.7.0",
"#hapi/joi": "^17.1.1",
"#sendgrid/mail": "^7.2.2",
"async-middleware": "^1.2.1",
"axios": "^0.19.2",
"bcrypt": "^3.0.4",
"bluebird": "^3.5.3",
"body-parser": "^1.18.3",
"bootstrap-star-rating": "^4.0.6",
"browser-sync": "^2.26.12",
"concurrently": "^4.1.0",
"configurable-date-input-polyfill": "^2.8.2",
"connect-redis": "^3.4.0",
"cookie-parser": "^1.4.5",
"debug": "~2.6.9",
"del": "^3.0.0",
"dotenv": "^6.2.0",
"ejs": "~2.5.7",
"ejs-lint": "^1.1.0",
"excel4node": "^1.7.2",
"express": "~4.16.0",
"express-async-handler": "^1.1.4",
"express-ejs-layouts": "^2.5.0",
"express-fileupload": "^1.1.6",
"express-session": "^1.17.1",
"express-subdomain": "^1.0.5",
"firebase": "^7.17.1",
"firebase-admin": "^8.13.0",
"geo-tz": "^6.0.0",
"geolib": "^3.3.1",
"gulp": "^4.0.2",
"gulp-autoprefixer": "^5.0.0",
"gulp-babel": "^8.0.0",
"gulp-cache": "^1.0.2",
"gulp-clean-css": "^3.9.4",
"gulp-csscomb": "^3.0.8",
"gulp-cssnano": "^2.1.3",
"gulp-html-prettify": "0.0.1",
"gulp-imagemin": "^4.1.0",
"gulp-npm-dist": "^1.0.1",
"gulp-postcss": "^7.0.1",
"gulp-rename": "^1.2.2",
"gulp-run": "^1.7.1",
"gulp-sass": "^3.2.1",
"gulp-sourcemaps": "^2.6.5",
"gulp-uglify": "^3.0.0",
"gulp-useref-plus": "0.0.8",
"gulp-util": "^3.0.8",
"gulp-wait": "0.0.2",
"http-errors": "~1.6.2",
"input-time-polyfill": "^1.0.7",
"joi": "^14.3.1",
"joi-password-complexity": "4.1.0",
"knex": "^0.16.5",
"moment": "^2.27.0",
"moment-timezone": "^0.5.31",
"multer": "^1.4.2",
"node-cron": "^2.0.3",
"node-geocoder": "^3.27.0",
"nodemailer": "^6.4.10",
"passport": "^0.4.0",
"passport-local": "^1.0.0",
"pg": "^7.18.2",
"pino": "^5.17.0",
"pm2": "^3.2.9",
"postcss-flexbugs-fixes": "^3.3.1",
"streamifier": "^0.1.1",
"stripe": "^8.89.0",
"twilio": "^3.48.1",
"which-browser": "^0.5.1"
},
"devDependencies": {
"eslint": "^5.13.0",
"eslint-config": "^0.3.0",
"eslint-config-airbnb": "^17.1.0",
"eslint-config-prettier": "^4.0.0",
"eslint-plugin-import": "^2.22.0",
"eslint-plugin-prettier": "^3.1.4",
"husky": "^1.3.1",
"lint-staged": "^8.1.3",
"pino-pretty": "^2.5.0",
"prettier": "^1.16.4",
"pretty-quick": "^1.10.0",
"stylelint": "^9.10.1",
"stylelint-config-standard": "^18.2.0"
},
"lint-staged": {
"src/**/*.{js,jsx}": [
"eslint --fix",
"prettier --config .prettierrc --write",
"git add"
],
"packages/**/*.{js,jsx}": [
"eslint --fix",
"prettier --config .prettierrc --write",
"git add"
]
},
"husky": {
"hooks": {
"pre-commit": "lint-staged"
}
}
}
I then ran "npm i concurrently" and get this:
npm WARN deprecated #types/vfile-message#2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.
npm WARN deprecated stable#0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated source-map-url#0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated flatten#1.0.3: flatten is deprecated in favor of utility frameworks such as lodash.
npm WARN deprecated topo#3.0.3: This module has moved and is now available at #hapi/topo. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated #hapi/pinpoint#2.0.0: Moved to 'npm install #sideway/pinpoint'
npm WARN deprecated har-validator#5.1.5: this library is no longer supported
npm WARN deprecated urix#0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated #hapi/formula#2.0.0: Moved to 'npm install #sideway/formula'
npm WARN deprecated request-promise#4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated resolve-url#0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated hoek#6.1.3: This module has moved and is now available at #hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated browserslist#1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated gulp-util#0.0.1: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated source-map-resolve#0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated circular-json#0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated minimatch#0.2.12: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated gulp-util#3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated multer#1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated node-uuid#1.4.0: Use uuid module instead
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated minimatch#0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated #hapi/address#4.1.0: Moved to 'npm install #sideway/address'
npm WARN deprecated fsevents#1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar#2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated debug#4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated uuid#2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#2.0.3: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid#3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated mkdirp#0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated bcrypt#3.0.8: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated #babel/polyfill#7.12.1: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the #babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated text-encoding#0.6.4: no longer maintained
npm WARN deprecated node-pre-gyp#0.14.0: Please upgrade to #mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the #mapbox scoped package will recieve updates in the future
npm WARN deprecated axios#0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated joi#14.3.1: This module has moved and is now available at #hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.
npm WARN deprecated #hapi/joi#17.1.1: Switch to 'npm install joi'
npm WARN deprecated svgo#0.7.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated tar#2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated core-js#2.6.12: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js#3.6.5: core-js#<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-sass
npm ERR! command failed
npm ERR! command sh -c node scripts/build.js
npm ERR! Building: /Users/ttsssss/.nvm/versions/node/v16.0.0/bin/node /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli '/Users/ttsssss/.nvm/versions/node/v16.0.0/bin/node',
npm ERR! gyp verb cli '/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-gyp/bin/node-gyp.js',
npm ERR! gyp verb cli 'rebuild',
npm ERR! gyp verb cli '--verbose',
npm ERR! gyp verb cli '--libsass_ext=',
npm ERR! gyp verb cli '--libsass_cflags=',
npm ERR! gyp verb cli '--libsass_ldflags=',
npm ERR! gyp verb cli '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using node-gyp#3.8.0
npm ERR! gyp info using node#16.0.0 | darwin | arm64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb `which` failed Error: not found: python2
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:194:21)
npm ERR! gyp verb `which` failed python2 Error: not found: python2
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:194:21) {
npm ERR! gyp verb `which` failed code: 'ENOENT'
npm ERR! gyp verb `which` failed }
npm ERR! gyp verb check python checking for Python executable "python" in the PATH
npm ERR! gyp verb `which` failed Error: not found: python
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:194:21)
npm ERR! gyp verb `which` failed python Error: not found: python
npm ERR! gyp verb `which` failed at getNotFoundError (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:13:12)
npm ERR! gyp verb `which` failed at F (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:68:19)
npm ERR! gyp verb `which` failed at E (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:80:29)
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:89:16
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/index.js:42:5
npm ERR! gyp verb `which` failed at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/mode.js:8:5
npm ERR! gyp verb `which` failed at FSReqCallback.oncomplete (node:fs:194:21) {
npm ERR! gyp verb `which` failed code: 'ENOENT'
npm ERR! gyp verb `which` failed }
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-gyp/lib/configure.js:484:19)
npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-gyp/lib/configure.js:406:16)
npm ERR! gyp ERR! stack at F (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:68:16)
npm ERR! gyp ERR! stack at E (/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:80:29)
npm ERR! gyp ERR! stack at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/which/which.js:89:16
npm ERR! gyp ERR! stack at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/index.js:42:5
npm ERR! gyp ERR! stack at /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/isexe/mode.js:8:5
npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:194:21)
npm ERR! gyp ERR! System Darwin 21.5.0
npm ERR! gyp ERR! command "/Users/ttsssss/.nvm/versions/node/v16.0.0/bin/node" "/Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd /Users/ttsssss/Documents/HOZ-Repos/HOZ-Landingpage/hoz-test/node_modules/node-sass
npm ERR! gyp ERR! node -v v16.0.0
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/ttsssss/.npm/_logs/2022-07-28T19_34_07_226Z-debug.log
So I run npm outdated and get this:
Package Current Wanted Latest Location Depended by
#babel/core MISSING 7.18.9 7.18.9 - hoz-test
#babel/preset-env MISSING 7.18.9 7.18.9 - hoz-test
#google-cloud/firestore MISSING 3.8.6 5.0.2 - hoz-test
#google-cloud/storage MISSING 4.7.2 6.2.3 - hoz-test
#hapi/joi MISSING 17.1.1 17.1.1 - hoz-test
#sendgrid/mail MISSING 7.7.0 7.7.0 - hoz-test
async-middleware MISSING 1.2.1 1.2.1 - hoz-test
axios MISSING 0.19.2 0.27.2 - hoz-test
bcrypt MISSING 3.0.8 5.0.1 - hoz-test
bluebird MISSING 3.7.2 3.7.2 - hoz-test
body-parser MISSING 1.20.0 1.20.0 - hoz-test
bootstrap-star-rating MISSING 4.1.2 4.1.2 - hoz-test
browser-sync MISSING 2.27.10 2.27.10 - hoz-test
concurrently MISSING 4.1.2 7.3.0 - hoz-test
configurable-date-input-polyfill MISSING 2.8.2 3.1.4 - hoz-test
connect-redis MISSING 3.4.2 6.1.3 - hoz-test
cookie-parser MISSING 1.4.6 1.4.6 - hoz-test
debug MISSING 2.6.9 4.3.4 - hoz-test
del MISSING 3.0.0 7.0.0 - hoz-test
dotenv MISSING 6.2.0 16.0.1 - hoz-test
ejs MISSING 2.5.9 3.1.8 - hoz-test
ejs-lint MISSING 1.2.2 1.2.2 - hoz-test
excel4node MISSING 1.8.0 1.8.0 - hoz-test
express MISSING 4.16.4 4.18.1 - hoz-test
express-async-handler MISSING 1.2.0 1.2.0 - hoz-test
express-ejs-layouts MISSING 2.5.1 2.5.1 - hoz-test
express-fileupload MISSING 1.4.0 1.4.0 - hoz-test
express-session MISSING 1.17.3 1.17.3 - hoz-test
express-subdomain MISSING 1.0.5 1.0.5 - hoz-test
firebase MISSING 7.24.0 9.9.1 - hoz-test
firebase-admin MISSING 8.13.0 11.0.0 - hoz-test
geo-tz MISSING 6.0.2 7.0.2 - hoz-test
geolib MISSING 3.3.3 3.3.3 - hoz-test
gulp MISSING 4.0.2 4.0.2 - hoz-test
gulp-autoprefixer MISSING 5.0.0 8.0.0 - hoz-test
gulp-babel MISSING 8.0.0 8.0.0 - hoz-test
gulp-cache MISSING 1.1.3 1.1.3 - hoz-test
gulp-clean-css MISSING 3.10.0 4.3.0 - hoz-test
gulp-csscomb MISSING 3.1.0 3.1.0 - hoz-test
gulp-cssnano MISSING 2.1.3 2.1.3 - hoz-test
gulp-html-prettify MISSING 0.0.1 0.0.1 - hoz-test
gulp-imagemin MISSING 4.1.0 8.0.0 - hoz-test
gulp-npm-dist MISSING 1.0.3 1.0.3 - hoz-test
gulp-postcss MISSING 7.0.1 9.0.1 - hoz-test
gulp-rename MISSING 1.4.0 2.0.0 - hoz-test
gulp-run MISSING 1.7.1 1.7.1 - hoz-test
gulp-sass MISSING 3.2.1 5.1.0 - hoz-test
gulp-sourcemaps MISSING 2.6.5 3.0.0 - hoz-test
gulp-uglify MISSING 3.0.2 3.0.2 - hoz-test
gulp-useref-plus MISSING 0.0.8 0.0.8 - hoz-test
gulp-util MISSING 3.0.8 3.0.8 - hoz-test
gulp-wait MISSING 0.0.2 0.0.2 - hoz-test
http-errors MISSING 1.6.3 2.0.0 - hoz-test
input-time-polyfill MISSING 1.0.7 1.0.7 - hoz-test
joi MISSING 14.3.1 17.6.0 - hoz-test
joi-password-complexity MISSING 4.1.0 5.1.0 - hoz-test
knex MISSING 0.16.5 2.2.0 - hoz-test
moment MISSING 2.29.4 2.29.4 - hoz-test
moment-timezone MISSING 0.5.34 0.5.34 - hoz-test
multer MISSING 1.4.4 1.4.5-lts.1 - hoz-test
node-cron MISSING 2.0.3 3.0.1 - hoz-test
node-geocoder MISSING 3.29.0 4.2.0 - hoz-test
nodemailer MISSING 6.7.7 6.7.7 - hoz-test
passport MISSING 0.4.1 0.6.0 - hoz-test
passport-local MISSING 1.0.0 1.0.0 - hoz-test
pg MISSING 7.18.2 8.7.3 - hoz-test
pino MISSING 5.17.0 8.3.1 - hoz-test
pm2 MISSING 3.5.2 5.2.0 - hoz-test
postcss-flexbugs-fixes MISSING 3.3.1 5.0.2 - hoz-test
streamifier MISSING 0.1.1 0.1.1 - hoz-test
stripe MISSING 8.222.0 9.16.0 - hoz-test
twilio MISSING 3.80.0 3.80.0 - hoz-test
which-browser MISSING 0.5.1 0.7.0 - hoz-test
This question already has answers here:
Unable to install react-beautiful-dnd package
(2 answers)
Closed 1 year ago.
I'm trying to install the following package, which is well known.
However, I'm a little confused as to how to diagnose this issue. I'd like to use this package as it's a core concept of my site, drag and drop.
Is this saying I need react #16.14.0? How would I go about bumping the entire project up correctly? Will this cause issues with other packages?
I am quite new to React and specifically this concept of tree dependencies? I also know my packages may be messed up, and if I need to, I'm happy to try resolve with tips.
npm i react-beautiful-dnd
However I get these errors:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: new#0.1.0
npm ERR! Found: react#16.8.0
npm ERR! node_modules/react
npm ERR! peer react#">=16.8.0" from #emotion/react#11.7.0
npm ERR! node_modules/#emotion/react
npm ERR! peer #emotion/react#"^11.0.0-rc.0" from #emotion/styled#11.6.0
npm ERR! node_modules/#emotion/styled
npm ERR! peerOptional #emotion/styled#"^11.3.0" from #mui/material#5.2.3
npm ERR! node_modules/#mui/material
npm ERR! peer #mui/material#"^5.0.0" from #mui/icons-material#5.2.4
npm ERR! node_modules/#mui/icons-material
npm ERR! 1 more (the root project)
npm ERR! 3 more (#mui/styled-engine, #mui/system, the root project)
npm ERR! peerOptional #emotion/react#"^11.5.0" from #mui/material#5.2.3
npm ERR! node_modules/#mui/material
npm ERR! peer #mui/material#"^5.0.0" from #mui/icons-material#5.2.4
npm ERR! node_modules/#mui/icons-material
npm ERR! #mui/icons-material#"^5.2.4" from the root project
npm ERR! 1 more (the root project)
npm ERR! 3 more (#mui/styled-engine, #mui/system, the root project)
npm ERR! peer react#">=16.8.0" from #emotion/styled#11.6.0
npm ERR! node_modules/#emotion/styled
npm ERR! peerOptional #emotion/styled#"^11.3.0" from #mui/material#5.2.3
npm ERR! node_modules/#mui/material
npm ERR! peer #mui/material#"^5.0.0" from #mui/icons-material#5.2.4
npm ERR! node_modules/#mui/icons-material
npm ERR! #mui/icons-material#"^5.2.4" from the root project
npm ERR! 1 more (the root project)
npm ERR! peerOptional #emotion/styled#"^11.3.0" from #mui/styled-engine#5.2.0
npm ERR! node_modules/#mui/styled-engine
npm ERR! #mui/styled-engine#"^5.2.0" from #mui/system#5.2.3
npm ERR! node_modules/#mui/system
npm ERR! #mui/system#"^5.2.3" from #mui/material#5.2.3
npm ERR! node_modules/#mui/material
npm ERR! 2 more (#mui/system, the root project)
npm ERR! 22 more (#material-ui/core, #material-ui/icons, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! react-beautiful-dnd#"*" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react#16.14.0
npm ERR! node_modules/react
npm ERR! peer react#"^16.8.5 || ^17.0.0" from react-beautiful-dnd#13.1.0
npm ERR! node_modules/react-beautiful-dnd
npm ERR! react-beautiful-dnd#"*" 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.
It's worth noting my package.json looks:
{
"name": "new",
"version": "0.1.0",
"private": true,
"dependencies": {
"#emotion/react": "^11.7.0",
"#emotion/styled": "^11.6.0",
"#fontsource/roboto": "^4.5.1",
"#material-ui/icons": "^4.11.2",
"#mui/icons-material": "^5.2.4",
"#mui/material": "^5.2.3",
"#testing-library/jest-dom": "^5.11.4",
"#testing-library/react": "^11.1.0",
"#testing-library/user-event": "^12.1.10",
"framer-motion": "^4.1.17",
"gsap": "^3.9.1",
"material-ui-search-bar": "^1.0.0",
"react": "^16.8.0",
"react-dom": "^16.8.0",
"react-draggable": "^4.4.4",
"react-intersection-observer": "^8.33.1",
"react-scripts": "4.0.3",
"react-typewriter-effect": "^1.1.0",
"styled-components": "^5.3.3",
"typewriter-effect": "^2.18.2",
"web-vitals": "^1.0.1"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": [
"react-app",
"react-app/jest"
]
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
Is this saying I need react #16.14.0? How would I go about bumping the entire project up correctly? Will this cause issues with other packages?
Maybe your problem could be solved by removing the node_modules folder and running npm -g install npm, like this tutorial suggest: Unable to install react-beautiful-dnd package
I am working on a project for an internship on Angular and after trying to install a few modules from NgPrime I m getting the following errors every time I run an npm install regarding:
node-sass(cannot download)
node-gyp
Here is what I get after running npm install:
> node-sass#4.10.0 install C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\#angular-devkit\build-angular\node_modules\node-sass
> node scripts/install.js
Downloading binary from https://github.com/sass/node-sass/releases/download/v4.10.0/win32-x64-72_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.10.0/win32-x64-72_binding.node":
HTTP error 404 Not Found
Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.
export HTTP_PROXY=http://example.com:1234
or configure npm proxy via
npm config set proxy http://example.com:8080
> node-sass#4.10.0 postinstall C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\#angular-devkit\build-angular\node_modules\node-sass
> node scripts/build.js
Building: C:\Program Files\nodejs\node.exe C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli 'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli 'C:\\Users\\flaviu.cristian\\Desktop\\BSS\\TrackGPS.BSS.Web\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library='
gyp verb cli ]
gyp info using node-gyp#3.8.0
gyp info using node#12.18.3 | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe" in the PATH
gyp verb `which` failed Error: not found: C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe
gyp verb `which` failed at getNotFoundError (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:13:12)
gyp verb `which` failed at F (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:68:19)
gyp verb `which` failed at E (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:80:29)
gyp verb `which` failed at C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:89:16
gyp verb `which` failed at C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\isexe\index.js:42:5
gyp verb `which` failed at C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\isexe\windows.js:36:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:168:21)
gyp verb `which` failed C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe Error: not found: C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe
gyp verb `which` failed at getNotFoundError (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:13:12)
gyp verb `which` failed at F (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:68:19)
gyp verb `which` failed at E (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:80:29)
gyp verb `which` failed at C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\which\which.js:89:16
gyp verb `which` failed at C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\isexe\index.js:42:5
gyp verb `which` failed at C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\isexe\windows.js:36:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:168:21) {
gyp verb `which` failed code: 'ENOENT'
gyp verb `which` failed }
gyp verb could not find "C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe". checking python launcher
gyp verb could not find "C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "C:\Users\flaviu.cristian\.windows-build-tools\python27\python.exe", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\node-gyp\lib\configure.js:484:19)
gyp ERR! stack at PythonFinder.<anonymous> (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\node-gyp\lib\configure.js:509:16)
gyp ERR! stack at callback (C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\graceful-fs\polyfills.js:295:20)
gyp ERR! stack at FSReqCallback.oncomplete (fs.js:168:21)
gyp ERR! System Windows_NT 10.0.18363
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\flaviu.cristian\\Desktop\\BSS\\TrackGPS.BSS.Web\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\flaviu.cristian\Desktop\BSS\TrackGPS.BSS.Web\node_modules\#angular-devkit\build-angular\node_modules\node-sass
gyp ERR! node -v v12.18.3
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN #angular/core#7.2.16 requires a peer of zone.js#~0.8.26 but none is installed. You must install peer dependencies yourself.
npm WARN ajv-keywords#3.5.2 requires a peer of ajv#^6.9.1 but none is installed. You must install peer dependencies yourself.
npm WARN ng-snotify#4.3.1 requires a peer of #angular/core#^4.0.0 || ^5.0.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ng-snotify#4.3.1 requires a peer of zone.js#^0.8.4 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.13 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#2.1.3 (node_modules\watchpack\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-sass#4.10.0 (node_modules\#angular-devkit\build-angular\node_modules\node-sass):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-sass#4.10.0 postinstall: `node scripts/build.js`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
audited 1278 packages in 22.376s
12 packages are looking for funding
run `npm fund` for details
found 13 vulnerabilities (6 low, 4 moderate, 3 high)
run `npm audit fix` to fix them, or `npm audit` for details
Here is my package.json
{
"name": "TrackGPS.BSS",
"version": "8.0.0",
"scripts": {
"ng": "ng",
"start": "ng serve --configuration=local",
"build-local": "node --max-old-space-size=6144 ./node_modules/#angular/cli/bin/ng build --prod --configuration=local",
"build-dev": "node --max-old-space-size=6144 ./node_modules/#angular/cli/bin/ng build --prod --configuration=dev",
"build-test": "node --max-old-space-size=6144 ./node_modules/#angular/cli/bin/ng build --prod --configuration=test",
"build-prod": "node --max-old-space-size=6144 ./node_modules/#angular/cli/bin/ng build --prod",
"test": "ng test",
"lint": "ng lint",
"e2e": "ng e2e"
},
"private": true,
"dependencies": {
"#angular/animations": "^7.1.0",
"#angular/cdk": "^7.1.1",
"#angular/common": "^7.1.0",
"#angular/compiler": "^7.1.0",
"#angular/core": "^7.1.0",
"#angular/forms": "^7.1.0",
"#angular/platform-browser": "^7.1.0",
"#angular/platform-browser-dynamic": "^7.1.0",
"#angular/router": "^7.1.0",
"#fullcalendar/core": "^4.3.1",
"#fullcalendar/daygrid": "^4.3.0",
"#fullcalendar/interaction": "4.0.2",
"#fullcalendar/timegrid": "4.0.1",
"chart.js": "2.7.3",
"core-js": "^2.5.4",
"intl": "1.2.5",
"primeflex": "1.0.0-rc.1",
"primeicons": "1.0.0",
"primeng": "7.1.3",
"prismjs": "1.15.0",
"quill": "1.1.8",
"rxjs": "6.4.0",
"url-search-params-polyfill": "^6.0.0",
"web-animations-js": "2.3.1",
"zone.js": "0.9.1"
},
"devDependencies": {
"#angular-devkit/build-angular": "^0.11.0",
"#angular/cli": "~7.1.1",
"#angular/compiler-cli": "^7.1.0",
"#angular/language-service": "~7.1.0",
"#auth0/angular-jwt": "^2.1.0",
"#types/jasmine": "~2.8.8",
"#types/jasminewd2": "~2.0.3",
"#types/node": "~8.9.4",
"angular-l10n": "^7.2.0",
"angular-oauth2-oidc": "^5.0.2",
"codelyzer": "~4.5.0",
"jasmine-core": "~2.99.1",
"jasmine-spec-reporter": "~4.2.1",
"karma": "~3.1.1",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage-istanbul-reporter": "~2.0.1",
"karma-jasmine": "~1.1.2",
"karma-jasmine-html-reporter": "^0.2.2",
"ng-snotify": "^4.3.1",
"protractor": "~5.4.0",
"ts-node": "~7.0.0",
"tslint": "~5.11.0",
"typescript": "~3.1.6",
"webpack": "^4.41.2"
}
}
Initially after downloading the project and running for the first time npm install everything worked fine.I have tried to get back to my previous commit on git where everything was working but it did not solve my problem.
If there is any file that would might help you get a better understanding of the errors I will gladly post it
v4.10.0/win32-x64-72_binding.node - simply does not exist.
As far as I can tell - you can only use a certain node-sass version range with a specific Node.Js version.
https://github.com/sass/node-sass#supported-nodejs-versions-vary-by-release-please-consult-the-releases-page-below-is-a-quick-guide-for-minimum-support
So in your case: When you are using Node 12 - you must update to node-sass#4.12
This should get rid of the errors.
This is explained in the repos FAQ:
https://github.com/sass/node-sass/blob/master/TROUBLESHOOTING.md#404s
NPM version is outdated.
That is the reason that not find the dependency.
After searching all over the places finally I found the solution
npm install -g npm#latest
Before my last pull I was able to install npm packages with sudo npm install
The last package I installed was dotenv. I can't imagine that would cause this problem but I can't say for sure.
but now I am getting the EACCES error even if I use root.
I removed the entire directory and cloned again with no luck.
server: digitaloceal Ubuntu 16.04
deployment method: Git
ERROR MESSAGES
USER#uhr:/var/www/mysite$ sudo npm install
> buffertools#2.1.6 install /var/www/mysite/node_modules/buffertools
> node-gyp rebuild
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/var/www/mysite/node_modules/buffertools/build'
gyp ERR! System Linux 4.4.0-139-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /var/www/mysite/node_modules/buffertools
gyp ERR! node -v v10.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
> node-expat#2.3.17 install /var/www/mysite/node_modules/node-expat
> node-gyp rebuild
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/var/www/mysite/node_modules/node-expat/build'
gyp ERR! System Linux 4.4.0-139-generic
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /var/www/mysite/node_modules/node-expat
gyp ERR! node -v v10.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN mysite#1.0.0 No description
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: buffertools#2.1.6 (node_modules/buffertools):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: buffertools#2.1.6 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-expat#2.3.17 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-expat#2.3.17 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/USER/.npm/_logs/2018-11-23T17_51_52_704Z-debug.log
package.json
{
"name": "MYSITE",
"version": "1.0.0",
"description": "",
"main": "app.js",
"dependencies": {
"async": "^2.6.1",
"bcrypt": "^3.0.2",
"bcryptjs": "^2.4.3",
"bluebird": "^3.5.3",
"body-parser": "^1.18.3",
"cors": "^2.8.4",
"dotenv": "^6.1.0",
"express": "^4.16.4",
"express-session": "^1.15.6",
"jsonwebtoken": "latest",
"lodash": "^4.17.11",
"mongoose": "^5.3.7",
"nodemailer": "^4.6.8",
"passport": "^0.4.0",
"passport-jwt": "^4.0.0",
"request": "^2.88.0",
"rets-client": "^5.2.3",
"socket.io": "^2.1.1",
"through2": "^3.0.0",
"underscore": "^1.9.1"
},
"devDependencies": {},
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"repository": {
"type": "git",
"url": "MYREPO"
},
"author": "",
"license": "UNLICENSED",
"bugs": {
"url": "MYREPO"
},
"homepage": "MYREPO"
}
I want to run a webpack project within Vagrant (installed on Windows 10) where I embedded a Ubuntu 16.04 virtual machine.
I was able to install npm 5.6.0 and nodejs v8.9.4 very successfully.
I tried to run npm install to install all my dependencies. After getting these errors :
...
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
gyp ERR! stack at emitTwo (events.js:126:13)
gyp ERR! stack at ChildProcess.emit (events.js:214:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
gyp ERR! System Linux 4.4.0-116-generic
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /vagrant/src/my_project/static/node_modules/contextify
gyp ERR! node -v v8.9.4
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
...
I tried : npm install --no-bin-links, which gave me the same kind of erros above.
So I then run : npm run build
And now I keep getting this error :
sh: 1: rimraf: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! my-project#1.0.0 clean: `rimraf dist`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the my-project#1.0.0 clean script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2018-03-04T04_44_09_988Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-project#1.0.0 build: `npm run clean && webpack`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-project#1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2018-03-04T04_44_10_048Z-debug.log
Here is my package.json :
{
"name": "my-project",
"version": "1.0.0",
"description": "project",
"main": "index.js",
"scripts": {
"clean": "rimraf dist",
"build": "npm run clean && webpack",
"serve": "webpack-dev-server"
},
"repository": "",
"author": "Edgar KAMDEM",
"license": "ISC",
"dependencies": {
"acorn": "^5.5.0",
"axios": "^0.17.1",
"bootstrap": "^4.0.0-alpha.6",
"fabric": "^1.7.22",
"file-loader": "^1.1.5",
"font-awesome": "^4.7.0",
"jquery": "^3.2.1",
"jquery-ui-dist": "^1.12.1",
"lodash": "^4.17.4",
"mxgraph": "^3.8.0",
"popper.js": "^1.12.9",
"react": "^16.2.0",
"react-dom": "^16.2.0",
"react-input-range": "^1.2.2",
"react-redux": "^5.0.6",
"react-router": "^4.2.0",
"react-router-dom": "^4.2.2",
"redux": "^3.7.2",
"redux-form": "^7.2.0",
"redux-promise": "^0.5.3",
"redux-thunk": "^2.2.0"
},
"devDependencies": {
"autoprefixer": "^7.1.6",
"babel-core": "^6.26.0",
"babel-loader": "^7.1.2",
"css-loader": "^0.28.7",
"extract-text-webpack-plugin": "^3.0.2",
"html-webpack-plugin": "^2.30.1",
"node-sass": "^4.7.2",
"postcss-loader": "^2.0.9",
"precss": "^2.0.0",
"rimraf": "^2.6.2",
"sass-loader": "^6.0.6",
"style-loader": "^0.19.0",
"webpack": "^3.11.0",
"webpack-dev-server": "^2.11.2"
}
}
Don't know what to do, I'm lost. I tried everything on Google (Github, SO etc). Nothing work.
Please help!
Just add this script to your package.json:
"scripts": {
...
"rimraf": "./node_modules/rimraf/bin.js",
}
The current behavior is looking for globally installed rimraf (you can do it as well by executing npm i -g rimraf), but the line above says it should use local project's version.
In some rare cases, npm install -g #angular/cli#latest will fail to create the file bin.js in the following location
C:\Users\{{user}}\AppData\Roaming\npm\node_modules\rimraf
So try creating the missed file first by running the following command
npm i -g rimraf
Now you can run npm install -g #angular/cli#latest and it will install angular without any problems