I don't seem to be able to update a deployment on my production server. The build error log says I have npm ERR! Missing for a lot of random packages that I don't recognize.
Any thoughts?
npm run dev locally works fine.
npm run build locally also works.
package.json:
{
"name": "frontend",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"#sendgrid/mail": "^7.6.0",
"axios": "^0.22.0",
"is-hotkey": "^0.1.8",
"jsonwebtoken": "^8.5.1",
"lodash.debounce": "^4.0.8",
"next": "^12.0.7",
"next-auth": "^4.0.0-beta.6",
"next-share": "^0.12.2",
"prop-types": "^15.7.2",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"sass": "^1.42.1",
"slate": "^0.66.5",
"slate-history": "^0.66.0",
"slate-hyperscript": "^0.67.0",
"slate-react": "^0.66.7",
"swr": "^1.2.2",
"zustand": "^3.5.13"
},
"devDependencies": {
"eslint": "^7.32.0",
"eslint-config-next": "11.1.2",
"eslint-config-prettier": "^8.3.0",
"eslint-plugin-react": "^7.26.1"
},
"peerDependencies": {
"postcss": "^8.2.15"
}
}
Truncated build log:
(Full build log is too long to post here but can be found at https://pastebin.com/X3QsT5Ub)
2023-01-03T05:23:32.941474763Z [34m╭────────────[34m[30m[44m git repo clone [0m[0m[34m───────────╼[0m
2023-01-03T05:23:32.941522581Z [34m│[0m [34m › fetching app source code[0m
2023-01-03T05:23:32.941527248Z [34m│[0m => Selecting branch "main"
2023-01-03T05:23:33.592330065Z [34m│[0m => Checking out commit "2aad59cbc2d09d76318d8aed38923d1343d3e687"
2023-01-03T05:23:33.639870414Z [34m│[0m
2023-01-03T05:23:33.642769027Z [34m│[0m [32m ✔ cloned repo to [35m/workspace[0m[0m
2023-01-03T05:23:33.668461263Z [34m╰────────────────────────────────────────╼[0m
2023-01-03T05:23:33.668489897Z
2023-01-03T05:23:33.813826428Z [34m › configuring build-time app environment variables:[0m
2023-01-03T05:23:33.813853591Z SENDGRID_REQUEST_API_KEY NEXTAUTH_URL JWT_SECRET TWITTER_CLIENT_ID SESSION_SECRET FACEBOOK_CLIENT_SECRET NEXT_PUBLIC_API_URL GOOGLE_CLIENT_ID NEXT_PUBLIC_GOOGLE_ANALYTICS SENDGRID_API_KEY TWITTER_CLIENT_SECRET GOOGLE_CLIENT_SECRET FACEBOOK_CLIENT_ID NEXT_PUBLIC_CDN_URL NEXT_PUBLIC_URL
2023-01-03T05:23:33.813858557Z
2023-01-03T05:23:33.816914126Z [34m › configuring custom build command to be run at the end of the build:[0m
2023-01-03T05:23:33.824312558Z [34m│[0m npm run build
2023-01-03T05:23:33.824325409Z
2023-01-03T05:23:33.939270524Z [34m╭────────────[34m[30m[44m buildpack detection [0m[0m[34m───────────╼[0m
2023-01-03T05:23:33.957886779Z [34m│[0m [34m › using Ubuntu 18.04 stack[0m
2023-01-03T05:23:34.335160381Z [34m│[0m Detected the following buildpacks suitable to build your app:
2023-01-03T05:23:34.335187887Z [34m│[0m
2023-01-03T05:23:34.335192227Z [34m│[0m heroku/nodejs-engine v0.5.1
2023-01-03T05:23:34.335195933Z [34m│[0m digitalocean/node v0.3.4 (Node.js)
2023-01-03T05:23:34.335198998Z [34m│[0m digitalocean/procfile v0.0.3 (Procfile)
2023-01-03T05:23:34.335201882Z [34m│[0m digitalocean/custom v0.1.1 (Custom Build Command)
2023-01-03T05:23:34.335204790Z [34m│[0m
2023-01-03T05:23:34.335208439Z [34m│[0m For documentation on the buildpacks used to build your app, please see:
2023-01-03T05:23:34.335211277Z [34m│[0m
2023-01-03T05:23:34.335214285Z [34m│[0m Node.js v0.3.4 https://do.co/apps-buildpack-node
2023-01-03T05:23:34.338731564Z [34m╰─────────────────────────────────────────────╼[0m
2023-01-03T05:23:34.338756219Z
2023-01-03T05:23:34.342499466Z [34m╭────────────[34m[30m[44m build caching [0m[0m[34m───────────╼[0m
2023-01-03T05:23:34.345203660Z [34m│[0m [34m › checking for cache from a previous build[0m
2023-01-03T05:23:36.349910107Z [34m│[0m Layer cache not found
2023-01-03T05:23:36.840439508Z [34m│[0m Restoring metadata for "heroku/nodejs-engine:nodejs" from app image
2023-01-03T05:23:38.022936715Z [34m│[0m Layer cache not found
2023-01-03T05:23:38.206441335Z [34m│[0m Removing "heroku/nodejs-engine:nodejs", not in cache
2023-01-03T05:23:38.228319066Z [34m╰───────────────────────────────────────╼[0m
2023-01-03T05:23:38.228345695Z
2023-01-03T05:23:38.231939436Z [34m╭────────────[34m[30m[44m app build [0m[0m[34m───────────╼[0m
2023-01-03T05:23:38.270899451Z [34m│[0m ---> Node.js Buildpack
2023-01-03T05:23:38.271778947Z [34m│[0m ---> Installing toolbox
2023-01-03T05:23:38.272990789Z [34m│[0m ---> - jq
2023-01-03T05:23:38.767230760Z [34m│[0m ---> - yj
2023-01-03T05:23:40.421610852Z [34m│[0m ---> Getting Node version
2023-01-03T05:23:40.426719023Z [34m│[0m ---> Resolving Node version
2023-01-03T05:23:41.576349974Z [34m│[0m ---> Downloading and extracting Node v16.19.0
2023-01-03T05:23:44.133555936Z [34m│[0m ---> Parsing package.json
2023-01-03T05:23:44.682951726Z [34m│[0m ---> No file to start server
2023-01-03T05:23:44.682986333Z [34m│[0m ---> either use 'docker run' to start container or add index.js or server.js
2023-01-03T05:23:44.705125940Z [34m│[0m Project contains package-lock.json, using npm
2023-01-03T05:23:45.186038000Z [34m│[0m Using npm v8.19.3. To configure a different version of npm, set the engines.npm property in package.json.
2023-01-03T05:23:45.186070065Z [34m│[0m See https://do.co/apps-buildpack-node for further instructions.
2023-01-03T05:23:45.186073642Z [34m│[0m Installing node_modules using npm (from package-lock.json)
2023-01-03T05:23:45.558705466Z [34m│[0m Running npm ci
2023-01-03T05:23:45.558734033Z [34m│[0m
2023-01-03T05:24:35.546488253Z [34m│[0m npm notice
2023-01-03T05:24:35.546897593Z [34m│[0m npm notice New major version of npm available! 8.19.3 -> 9.2.0
2023-01-03T05:24:35.546924246Z [34m│[0m npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.2.0>
2023-01-03T05:24:35.546928926Z [34m│[0m npm notice Run `npm install -g npm#9.2.0` to update!
2023-01-03T05:24:35.546933358Z [34m│[0m npm notice
2023-01-03T05:24:35.745769724Z [34m│[0m npm ERR! code EUSAGE
2023-01-03T05:24:36.132947911Z [34m│[0m npm ERR!
2023-01-03T05:24:36.132995675Z [34m│[0m npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
2023-01-03T05:24:36.133000833Z [34m│[0m npm ERR!
2023-01-03T05:24:36.133005170Z [34m│[0m npm ERR! Missing: react-scripts#4.0.3 from lock file
2023-01-03T05:24:36.133009345Z [34m│[0m npm ERR! Missing: #pmmmwh/react-refresh-webpack-plugin#0.4.3 from lock file
2023-01-03T05:24:36.133012622Z [34m│[0m npm ERR! Missing: react-refresh#0.8.3 from lock file
2023-01-03T05:24:36.133016415Z [34m│[0m npm ERR! Missing: webpack#4.44.2 from lock file
2023-01-03T05:24:36.133164448Z [34m│[0m npm ERR! Missing: type-fest#0.13.1 from lock file
2023-01-03T05:24:36.133195451Z [34m│[0m npm ERR! Missing: #svgr/webpack#5.5.0 from lock file
2023-01-03T05:24:36.217638704Z [34m│[0m npm ERR! Missing: rimraf#2.7.1 from lock file
2023-01-03T05:24:36.217643475Z [34m│[0m npm ERR! Missing: run-queue#1.0.3 from lock file
2023-01-03T05:24:36.217648027Z [34m│[0m npm ERR! Missing: iferr#0.1.5 from lock file
2023-01-03T05:24:36.217806649Z [34m│[0m npm ERR! Missing: rimraf#2.7.1 from lock file
2023-01-03T05:24:36.217823920Z [34m│[0m npm ERR! Missing: cyclist#1.0.1 from lock file
2023-01-03T05:24:36.217829162Z [34m│[0m npm ERR! Missing: pump#2.0.1 from lock file
2023-01-03T05:24:36.217833834Z [34m│[0m npm ERR! Missing: yallist#3.1.1 from lock file
2023-01-03T05:24:36.217837368Z [34m│[0m npm ERR! Missing: jsonfile#4.0.0 from lock file
2023-01-03T05:24:36.217841611Z [34m│[0m npm ERR! Missing: universalify#0.1.2 from lock file
2023-01-03T05:24:36.218012211Z [34m│[0m npm ERR! Missing: locate-path#5.0.0 from lock file
2023-01-03T05:24:36.218018480Z [34m│[0m npm ERR! Missing: path-exists#4.0.0 from lock file
2023-01-03T05:24:36.218023290Z [34m│[0m npm ERR! Missing: p-locate#4.1.0 from lock file
2023-01-03T05:24:36.218028050Z [34m│[0m npm ERR! Missing: p-limit#2.3.0 from lock file
2023-01-03T05:24:36.218032719Z [34m│[0m npm ERR! Missing: is-extendable#0.1.1 from lock file
2023-01-03T05:24:36.218037369Z [34m│[0m npm ERR! Missing: is-extendable#0.1.1 from lock file
2023-01-03T05:24:36.218042215Z [34m│[0m npm ERR! Missing: is-extendable#0.1.1 from lock file
2023-01-03T05:24:36.218212401Z [34m│[0m npm ERR! Missing: is-extendable#0.1.1 from lock file
2023-01-03T05:24:36.218226689Z [34m│[0m npm ERR! Missing: is-extendable#0.1.1 from lock file
2023-01-03T05:24:36.218245350Z [34m│[0m npm ERR! Missing: ansi-regex#4.1.1 from lock file
2023-01-03T05:24:36.218250343Z [34m│[0m npm ERR! Missing: ansi-regex#4.1.1 from lock file
2023-01-03T05:24:36.218385681Z [34m│[0m npm ERR! Missing: ansi-regex#4.1.1 from lock file
2023-01-03T05:24:36.218396179Z [34m│[0m npm ERR! Missing: is-extendable#0.1.1 from lock file
2023-01-03T05:24:36.218401143Z [34m│[0m npm ERR!
2023-01-03T05:24:36.218406825Z [34m│[0m npm ERR! Clean install a project
2023-01-03T05:24:36.218411320Z [34m│[0m npm ERR!
2023-01-03T05:24:36.218416947Z [34m│[0m npm ERR! Usage:
2023-01-03T05:24:36.218421023Z [34m│[0m npm ERR! npm ci
2023-01-03T05:24:36.218425306Z [34m│[0m npm ERR!
2023-01-03T05:24:36.218429863Z [34m│[0m npm ERR! Options:
2023-01-03T05:24:36.218512838Z [34m│[0m npm ERR! [-S|--save|--no-save|--save-prod|--save-dev|--save-optional|--save-peer|--save-bundle]
2023-01-03T05:24:36.218524674Z [34m│[0m npm ERR! [-E|--save-exact] [-g|--global] [--global-style] [--legacy-bundling]
2023-01-03T05:24:36.218530426Z [34m│[0m npm ERR! [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
2023-01-03T05:24:36.218534991Z [34m│[0m npm ERR! [--strict-peer-deps] [--no-package-lock] [--foreground-scripts]
2023-01-03T05:24:36.218540317Z [34m│[0m npm ERR! [--ignore-scripts] [--no-audit] [--no-bin-links] [--no-fund] [--dry-run]
2023-01-03T05:24:36.218729253Z [34m│[0m npm ERR! [-w|--workspace <workspace-name> [-w|--workspace <workspace-name> ...]]
2023-01-03T05:24:36.218736626Z [34m│[0m npm ERR! [-ws|--workspaces] [--include-workspace-root] [--install-links]
2023-01-03T05:24:36.218740402Z [34m│[0m npm ERR!
2023-01-03T05:24:36.218744170Z [34m│[0m npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
2023-01-03T05:24:36.218747870Z [34m│[0m npm ERR!
2023-01-03T05:24:36.218751678Z [34m│[0m npm ERR! Run "npm help ci" for more info
2023-01-03T05:24:36.224982603Z [34m│[0m
2023-01-03T05:24:36.225313808Z [34m│[0m npm ERR! A complete log of this run can be found in:
2023-01-03T05:24:36.225422736Z [34m│[0m npm ERR! /home/apps/.npm/_logs/2023-01-03T05_23_45_874Z-debug-0.log
2023-01-03T05:24:36.254075934Z [34m│[0m
2023-01-03T05:24:36.254115394Z [34m│[0m unable to invoke layer creator
2023-01-03T05:24:36.254122169Z [34m│[0m installing node_modules: exit status 1
2023-01-03T05:24:36.254968098Z [34m│[0m [31;1mERROR: [0mfailed to build: exit status 1
2023-01-03T05:24:36.408187117Z [34m│[0m
2023-01-03T05:24:36.411589784Z [34m│[0m
2023-01-03T05:24:36.411615123Z [34m│[0m For documentation on the buildpacks used to build your app, please see:
2023-01-03T05:24:36.411620053Z [34m│[0m
2023-01-03T05:24:36.411623774Z [34m│[0m Node.js v0.3.4 https://do.co/apps-buildpack-node
2023-01-03T05:24:36.412603777Z [34m│[0m
2023-01-03T05:24:36.424794044Z [34m│[0m [31m ✘ build failed[0m
Fixed... Steps I took:
Set my node and npm environment to be the same on local and production
Which led me to a new error and help page: https://nextjs.org/docs/messages/failed-loading-swc
Related
This question already has answers here:
Fix the upstream dependency conflict installing NPM packages
(15 answers)
Closed 5 months ago.
so since the project started the deploy never had a problem, and out of nowhere today this message started to appear on vercel...
the application was coded using next js
I searched and searched and couldn't find a solution that worked for me...
Cloning github.com/ThiagoC0STA/kfk (Branch: main, Commit: f69b855)
Cloning completed: 1.077s
Looking up build cache...
Build Cache not found
Running "vercel build"
Vercel CLI 28.2.2
Installing dependencies...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: react-elastic-carousel#0.11.5
npm ERR! Found: react#18.2.0
npm ERR! node_modules/react
npm ERR! react#"18.2.0" from the root project
npm ERR! peer react#"^17.0.2 || ^18.0.0-0" from next#12.2.5
npm ERR! node_modules/next
npm ERR! next#"12.2.5" from the root project
npm ERR! 5 more (react-dom, react-slick, styled-components, styled-jsx, use-sync-external-store)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"15 - 17" from react-elastic-carousel#0.11.5
npm ERR! node_modules/react-elastic-carousel
npm ERR! react-elastic-carousel#"^0.11.5" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react#17.0.2
npm ERR! node_modules/react
npm ERR! peer react#"15 - 17" from react-elastic-carousel#0.11.5
npm ERR! node_modules/react-elastic-carousel
npm ERR! react-elastic-carousel#"^0.11.5" 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 /vercel/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /vercel/.npm/_logs/2022-09-12T18_11_25_601Z-debug-0.log
Error: Command "npm install" exited with 1
package.json
{
"name": "kfk",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"next": "12.2.5",
"next-images": "^1.8.4",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-elastic-carousel": "^0.11.5",
"react-slick": "^0.29.0",
"slick-carousel": "^1.8.1",
"styled-components": "^5.3.5"
},
"devDependencies": {
"babel-plugin-styled-components": "^2.0.7",
"eslint": "8.22.0",
"eslint-config-next": "12.2.5"
}
}
I don't understand why I have this error out of the blue, since I've been deploying for weeks and this started out of nowhere.
Try running
npm install --legacy-peer-deps
If it's necessary, you can try to use --force
npm install --force
Here was the docs
Npm install --force
I am trying to install shadow-cljs in a MacOS Monterey 12.5. I am new to the Apple ecosystem, to npm, and Clojure/ClojureScript stack. This a new world for me.
This is the project folder, as you can see there is already a package.json file:
pedro#Pedros-MacBook-Air balance % ls -l1
LICENSE
README.md
config
dev.cljs.edn
docs
externs
firebase-deploy.my-instance-specific-variables.TEMPLATE.edn
firestore.rules.json
makefile
package-lock.json
package.json
project.clj
public
semantic
semantic.json
shadow-cljs.edn
src
tools
This is the content of the package.json file:
pedro#Pedros-MacBook-Air balance % cat package.json
{
"name": "xxxx",
"version": "0.3.0",
"description": "xxxx",
"repository": {
"type": "git",
"url": "xxxxxxxxxxxxx.com"
},
"author": {
"name": "xxxxxxxxx",
"email": "xxxxxxx"
},
"license": "unlicensed",
"scripts": {
"dev": "shadow-cljs watch app;",
"release": "shadow-cljs release app;",
"server": "shadow-cljs server;",
"clean": "rm -rf target; rm -rf public/js"
},
"dependencies": {
"#firebase/app": "^0.4.22",
"#firebase/auth": "^0.11.8",
"#firebase/database": "^0.4.12",
"#firebase/firestore": "^1.6.4",
"#firebase/logger": "^0.1.28",
"#firebase/webchannel-wrapper": "^0.2.29",
"#js-joda/core": "3.2.0",
"#js-joda/locale_en-us": "3.1.1",
"#js-joda/timezone": "2.2.0",
"#sheet/core": "^1.20191114.1",
"create-react-class": "^15.6.3",
"firebase": "5.7.3",
"highlight.js": "^9.16.2",
"process": "^0.11.10",
"react": "^16.11.0",
"react-dom": "^16.11.0",
"react-flip-move": "^3.0.4",
"react-highlight.js": "^1.0.7",
"reactstrap": "^8.6.0",
"semantic-ui": "^2.4.2",
"semantic-ui-react": "^0.82.5",
"smartystreets-javascript-sdk": "^1.9.2",
"stripe": "^8.158.0",
"tslib": "1.10.0"
},
"devDependencies": {
"shadow-cljs": "2.15.3"
}
}
The manual indicates:
If you have a package.json already and just want to add shadow-cljs
run NPM
$ npm install --save-dev shadow-cljs
Hence, I did:
pedro#Pedros-MacBook-Air balance % npm install --save-dev shadow-cljs
Which retrieved the following error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: #js-joda/timezone#2.2.0
npm ERR! Found: #js-joda/core#3.2.0
npm ERR! node_modules/#js-joda/core
npm ERR! peer #js-joda/core#">=1.11.0" from #js-joda/locale_en-us#3.1.1
npm ERR! node_modules/#js-joda/locale_en-us
npm ERR! #js-joda/locale_en-us#"3.1.1" from the root project
npm ERR! #js-joda/core#"3.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer #js-joda/core#"^1.11.0" from #js-joda/timezone#2.2.0
npm ERR! node_modules/#js-joda/timezone
npm ERR! peer #js-joda/timezone#"^2.2.0" from #js-joda/locale_en-us#3.1.1
npm ERR! node_modules/#js-joda/locale_en-us
npm ERR! #js-joda/locale_en-us#"3.1.1" from the root project
npm ERR! #js-joda/timezone#"2.2.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: #js-joda/core#1.12.0
npm ERR! node_modules/#js-joda/core
npm ERR! peer #js-joda/core#"^1.11.0" from #js-joda/timezone#2.2.0
npm ERR! node_modules/#js-joda/timezone
npm ERR! peer #js-joda/timezone#"^2.2.0" from #js-joda/locale_en-us#3.1.1
npm ERR! node_modules/#js-joda/locale_en-us
npm ERR! #js-joda/locale_en-us#"3.1.1" from the root project
npm ERR! #js-joda/timezone#"2.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 /Users/pedro/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pedro/.npm/_logs/2022-08-01T14_36_59_868Z-debug-0.log
After reading other questions on Stack Overflow around upstream dependency conflict, I tried without success the following:
pedro#Pedros-MacBook-Air balance % npm install --legacy-peer-deps --save-dev shadow-cljs
Which returned a different error message on querystring legacy:
pedro#Pedros-MacBook-Air balance % npm install --legacy-peer-deps --save-dev shadow-cljs
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm ERR! code 1
npm ERR! path /Users/pedro/projects/balance/node_modules/semantic-ui
npm ERR! command failed
npm ERR! command sh /var/folders/fh/7d_1drwd2ps3zw03j9ftkqs80000gn/T/install-64525ec5.sh
npm ERR! fs.js:47
npm ERR! } = primordials;
npm ERR! ^
npm ERR!
npm ERR! ReferenceError: primordials is not defined
npm ERR! at fs.js:47:5
npm ERR! at req_ (/Users/pedro/projects/balance/node_modules/natives/index.js:143:24)
npm ERR! at Object.req [as require] (/Users/pedro/projects/balance/node_modules/natives/index.js:55:10)
npm ERR! at Object.<anonymous> (/Users/pedro/projects/balance/node_modules/graceful-fs/fs.js:1:37)
npm ERR! at Module._compile (node:internal/modules/cjs/loader:1120:14)
npm ERR! at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
npm ERR! at Module.load (node:internal/modules/cjs/loader:998:32)
npm ERR! at Module._load (node:internal/modules/cjs/loader:839:12)
npm ERR! at Module.require (node:internal/modules/cjs/loader:1022:19)
npm ERR! at require (node:internal/modules/cjs/helpers:102:18)
npm ERR!
npm ERR! Node.js v18.7.0
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pedro/.npm/_logs/2022-08-01T14_45_00_773Z-debug-0.log
I also tried another suggestion:
pedro#Pedros-MacBook-Air balance % npm list --depth=3
Which retrieved:
tallyfor-balance#0.3.0 /Users/pedro/projects/balance
├── UNMET DEPENDENCY #firebase/app#^0.4.22
├── UNMET DEPENDENCY #firebase/auth#^0.11.8
├── UNMET DEPENDENCY #firebase/database#^0.4.12
├── UNMET DEPENDENCY #firebase/firestore#^1.6.4
├── UNMET DEPENDENCY #firebase/logger#^0.1.28
├── UNMET DEPENDENCY #firebase/webchannel-wrapper#^0.2.29
├── UNMET DEPENDENCY #js-joda/core#3.2.0
├── UNMET DEPENDENCY #js-joda/locale_en-us#3.1.1
├── UNMET DEPENDENCY #js-joda/timezone#2.2.0
├── UNMET DEPENDENCY #sheet/core#^1.20191114.1
├── UNMET DEPENDENCY create-react-class#^15.6.3
├── UNMET DEPENDENCY firebase#5.7.3
├── UNMET DEPENDENCY highlight.js#^9.16.2
├── UNMET DEPENDENCY process#^0.11.10
├── UNMET DEPENDENCY react-dom#^16.11.0
├── UNMET DEPENDENCY react-flip-move#^3.0.4
├── UNMET DEPENDENCY react-highlight.js#^1.0.7
├── UNMET DEPENDENCY react#^16.11.0
├── UNMET DEPENDENCY reactstrap#^8.6.0
├── UNMET DEPENDENCY semantic-ui-react#^0.82.5
├── UNMET DEPENDENCY semantic-ui#^2.4.2
├── UNMET DEPENDENCY shadow-cljs#2.15.3
├── UNMET DEPENDENCY smartystreets-javascript-sdk#^1.9.2
├── UNMET DEPENDENCY stripe#^8.158.0
└── UNMET DEPENDENCY tslib#1.10.0
npm ERR! code ELSPROBLEMS
npm ERR! missing: #firebase/app#^0.4.22, required by tallyfor-balance#0.3.0
npm ERR! missing: #firebase/auth#^0.11.8, required by tallyfor-balance#0.3.0
npm ERR! missing: #firebase/database#^0.4.12, required by tallyfor-balance#0.3.0
npm ERR! missing: #firebase/firestore#^1.6.4, required by tallyfor-balance#0.3.0
npm ERR! missing: #firebase/logger#^0.1.28, required by tallyfor-balance#0.3.0
npm ERR! missing: #firebase/webchannel-wrapper#^0.2.29, required by tallyfor-balance#0.3.0
npm ERR! missing: #js-joda/core#3.2.0, required by tallyfor-balance#0.3.0
npm ERR! missing: #js-joda/locale_en-us#3.1.1, required by tallyfor-balance#0.3.0
npm ERR! missing: #js-joda/timezone#2.2.0, required by tallyfor-balance#0.3.0
npm ERR! missing: #sheet/core#^1.20191114.1, required by tallyfor-balance#0.3.0
npm ERR! missing: create-react-class#^15.6.3, required by tallyfor-balance#0.3.0
npm ERR! missing: firebase#5.7.3, required by tallyfor-balance#0.3.0
npm ERR! missing: highlight.js#^9.16.2, required by tallyfor-balance#0.3.0
npm ERR! missing: process#^0.11.10, required by tallyfor-balance#0.3.0
npm ERR! missing: react-dom#^16.11.0, required by tallyfor-balance#0.3.0
npm ERR! missing: react-flip-move#^3.0.4, required by tallyfor-balance#0.3.0
npm ERR! missing: react-highlight.js#^1.0.7, required by tallyfor-balance#0.3.0
npm ERR! missing: react#^16.11.0, required by tallyfor-balance#0.3.0
npm ERR! missing: reactstrap#^8.6.0, required by tallyfor-balance#0.3.0
npm ERR! missing: semantic-ui-react#^0.82.5, required by tallyfor-balance#0.3.0
npm ERR! missing: semantic-ui#^2.4.2, required by tallyfor-balance#0.3.0
npm ERR! missing: shadow-cljs#2.15.3, required by tallyfor-balance#0.3.0
npm ERR! missing: smartystreets-javascript-sdk#^1.9.2, required by tallyfor-balance#0.3.0
npm ERR! missing: stripe#^8.158.0, required by tallyfor-balance#0.3.0
npm ERR! missing: tslib#1.10.0, required by tallyfor-balance#0.3.0
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pedro/.npm/_logs/2022-08-01T14_44_49_026Z-debug-0.log
pedro#Pedros-MacBook-Air balance % npm install --legacy-peer-deps --save-dev shadow-cljs
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm ERR! code 1
npm ERR! path /Users/pedro/projects/balance/node_modules/semantic-ui
npm ERR! command failed
npm ERR! command sh /var/folders/fh/7d_1drwd2ps3zw03j9ftkqs80000gn/T/install-64525ec5.sh
npm ERR! fs.js:47
npm ERR! } = primordials;
npm ERR! ^
npm ERR!
npm ERR! ReferenceError: primordials is not defined
npm ERR! at fs.js:47:5
npm ERR! at req_ (/Users/pedro/projects/balance/node_modules/natives/index.js:143:24)
npm ERR! at Object.req [as require] (/Users/pedro/projects/balance/node_modules/natives/index.js:55:10)
npm ERR! at Object.<anonymous> (/Users/pedro/projects/balance/node_modules/graceful-fs/fs.js:1:37)
npm ERR! at Module._compile (node:internal/modules/cjs/loader:1120:14)
npm ERR! at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
npm ERR! at Module.load (node:internal/modules/cjs/loader:998:32)
npm ERR! at Module._load (node:internal/modules/cjs/loader:839:12)
npm ERR! at Module.require (node:internal/modules/cjs/loader:1022:19)
npm ERR! at require (node:internal/modules/cjs/helpers:102:18)
npm ERR!
npm ERR! Node.js v18.7.0
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/pedro/.npm/_logs/2022-08-01T14_45_00_773Z-debug-0.log
Using the global flag also did not solve:
pedro#Pedros-MacBook-Air balance % npm install -g npm
changed 14 packages, and audited 202 packages in 1s
11 packages are looking for funding
run `npm fund` for details
I am unsure about what else to try.
Any suggestion? Did I miss something?
Observation.: I am able to successfully run the quick start example on GitHub README of shadow-cljs repo.
Last login: Mon Aug 1 16:40:55 on ttys000
pedro#Pedros-MacBook-Air ~ % cd projects
pedro#Pedros-MacBook-Air projects % cd acme-app
pedro#Pedros-MacBook-Air acme-app % npx shadow-cljs node-repl
shadow-cljs - config: /Users/pedro/projects/acme-app/shadow-cljs.edn
shadow-cljs - server version: 2.19.8 running at http://localhost:9630
shadow-cljs - nREPL server started on port 50748
cljs.user=> shadow-cljs - #4 ready!
(+ 99 1)
100
Thanks.
When you have an existing project like this you just run npm install, without any additional arguments, to install all the dependencies listed in package.json. npm ci also works, which is sort for clean-install, if you have an existing package-lock.json it'll ensure to install the exact versions that were previously used.
However, your project seems to be a bit dated which means that the npm version you use may be newer than the one used at the time the project was created. This is why you may need to run npm install --legacy-peer-deps instead.
When you do npm install shadow-cljs (or any other variant you tried) it'll tell npm to only install shadow-cljs and ignore the rest, which explains all the unmet dependencies.
I have cloned a project from a Git Repo into my Mac, It only has project files not the node modules.
In GIT : Readme.md says run npm install to setup the project.
When I run the npm install I get below error list, how do I get through it?
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: #vue/eslint-config-standard#6.1.0
npm ERR! Found: eslint-plugin-vue#8.7.1
npm ERR! node_modules/eslint-plugin-vue
npm ERR! dev eslint-plugin-vue#"^8.0.3" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint-plugin-vue#"^7.0.0" from #vue/eslint-config-standard#6.1.0
npm ERR! node_modules/#vue/eslint-config-standard
npm ERR! dev #vue/eslint-config-standard#"^6.1.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: eslint-plugin-vue#7.20.0
npm ERR! node_modules/eslint-plugin-vue
npm ERR! peer eslint-plugin-vue#"^7.0.0" from #vue/eslint-config-standard#6.1.0
npm ERR! node_modules/#vue/eslint-config-standard
npm ERR! dev #vue/eslint-config-standard#"^6.1.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 /Users/dev/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/dev/.npm/_logs/2022-06-23T23_17_06_125Z-debug-0.log
This bug seems current, to reproduce it :
vue create hello-world
Vue CLI v5.0.8
...
npm install
and if you do : rm -rf node_modules then npm install you get error :
npm ERR! While resolving: #vue/eslint-config-standard#6.1.0
And no solution till now
thank you
What I did to get rid of the problem was removing the:
"eslint-plugin-vue": "^8.0.3",
line in the package.json file.
from the "devDependencies" section.
Then I did an
npm install
to download all the dependencies. And after that I downloaded the eslint Vue plugin seperatly with the Vue CLI.
vue add eslint
I don't know if this is the solution to the problem. I just wanted to help.
I want to use current Vuetify 3 version from master in my project.
I cloned vuetify from master (git clone -b next https://github.com/vuetifyjs/vuetify.git) to /home/pavel/vuetify folder. After that I installed vuetify project (yarn install) .
In my project I set
"dependencies": {
"vuetify": "file:/home/pavel/vuetify",
....
},
"devDependencies": {,
...
"vuetify-loader": "^2.0.0-alpha.0"
},
However, when I try to build my project I get:
$npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: my_project#0.1.0
npm ERR! Found: vuetify#undefined
npm ERR! node_modules/vuetify
npm ERR! vuetify#"file:/home/pavel/vuetify" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer vuetify#"^3.0.0-alpha.11" from vuetify-loader#2.0.0-alpha.9
npm ERR! node_modules/vuetify-loader
npm ERR! dev vuetify-loader#"^2.0.0-alpha.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.
Could anyone help to build and use current Vuetify 3 version from master.
You have to build it too (yarn build vuetify), and the vuetify package is under packages/vuetify, not the root of the repo.
If you just want to try the latest changes they're published automatically to npm: https://vuetifyjs.com/en/getting-started/installation/#nightly-builds
I'm having trouble setting up an NPM task for an automated build in Visual Studio Team Services (previously Visual Studio Online). There are two problems:
Cache locking errors (shown below).
It is painfully slow -- 45+ minutes for a dozen or so packages.
I added the --cache argument but that did not seem to help.
npm install --dev --cache $(Agent.BuildDirectory)\b
The binaries folder seems like the right spot for the cache, but honestly, I'm not sure. Some documentation here:
https://msdn.microsoft.com/Library/vs/alm/Build/scripts/variables#AgentVariables
I appreciate any advice...
Current Config:
Build console output:
Set workingFolder to default: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.97.1\tasks\Npm\0.2.7
##[debug]check path : C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.97.1\tasks\Npm\0.2.7\task.json
##[debug]set resource file to: C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\1.97.1\tasks\Npm\0.2.7\task.json
##[debug]system.culture=en-US
##[debug]check path : C:\Program Files\nodejs\npm.cmd
##[debug]npm=C:\Program Files\nodejs\npm.cmd
##[debug]cwd=C:\a\1\s\com.example.web
##[debug]path exists: C:\a\1\s\com.example.web
##[debug]command=install
##[debug]C:\Program Files\nodejs\npm.cmd arg: install
##[debug]arguments=--dev --cache C:\a\1\b
##[debug]C:\Program Files\nodejs\npm.cmd arg: --dev --cache C:\a\1\b
##[debug]exec tool: C:\Program Files\nodejs\npm.cmd
##[debug]Arguments:
##[debug] install
##[debug] --dev
##[debug] --cache
##[debug] C:\a\1\b
[command]C:\Program Files\nodejs\npm.cmd install --dev --cache C:\a\1\b
npm WARN deprecated graceful-fs#3.0.8: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs#^4.0.0 as soon as possible.
npm WARN deprecated sf-lint#1.0.2: Use eslint-config-simplifield instead.
npm WARN deprecated lodash#2.4.1: lodash#<3.0.0 is no longer maintained. Upgrade to lodash#^4.0.0.
npm WARN deprecated lodash#0.9.2: Grunt needs your help! See https://github.com/gruntjs/grunt/issues/1403.
npm ERR! addLocal Could not install C:\a\1\s\com.example.web\#shinnn\eslint-config#>=0.0.5 <0.0.6\fixtures
npm WARN deprecated phantomjs#2.1.3: Package renamed to phantomjs-prebuilt. Please update 'phantomjs' package references to 'phantomjs-prebuilt'
npm WARN peerDependencies The peer dependency qunitjs#^1.14.0 included from karma-qunit will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN package.json Dependency 'mocha' exists in both dependencies and devDependencies, using 'mocha#*' from dependencies
npm WARN package.json Dependency 'mocha' exists in both dependencies and devDependencies, using 'mocha#*' from dependencies
npm ERR! addLocal Could not install C:\a\1\s\com.example.web\#shinnn\eslint-config#>=0.0.4 <0.0.5\fixtures
> cson#1.6.2 preinstall C:\a\1\s\com.example.web\node_modules\gulp-uglify\node_modules\uglify-save-license\node_modules\grunt-replace\node_modules\applause\node_modules\cson
> node ./cyclic.js
npm WARN locking Error: EMFILE, open 'C:\a\1\b\_locks\strip-ansi-0bb45da2369f5768.lock.STALE.STALE.STALE'
npm WARN locking at Error (native)
npm WARN locking C:\a\1\b\_locks\strip-ansi-0bb45da2369f5768.lock failed { [Error: EMFILE, open 'C:\a\1\b\_locks\strip-ansi-0bb45da2369f5768.lock.STALE.STALE.STALE']
npm WARN locking errno: -4066,
npm WARN locking code: 'EMFILE',
npm WARN locking path: 'C:\\a\\1\\b\\_locks\\strip-ansi-0bb45da2369f5768.lock.STALE.STALE.STALE' }
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--dev" "--cache" "C:\\a\\1\\b"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
2016-03-30T14:15:17.4509244Z npm ERR! Attempt to unlock C:\a\1\s\com.example.web\node_modules\gulp-imagemin\node_modules\imagemin-pngquant\node_modules\pngquant-bin\node_modules\compare-size\node_modules\ava\node_modules\chalk\node_modules\strip-ansi, which hasn't been locked
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm WARN locking Error: EMFILE, open 'C:\a\1\b\_locks\ansi-styles-cedcc1e1e4774cd0.lock.STALE.STALE.STALE'
npm WARN locking at Error (native)
npm WARN locking C:\a\1\b\_locks\ansi-styles-cedcc1e1e4774cd0.lock failed { [Error: EMFILE, open 'C:\a\1\b\_locks\ansi-styles-cedcc1e1e4774cd0.lock.STALE.STALE.STALE']
npm WARN locking errno: -4066,
npm WARN locking code: 'EMFILE',
npm WARN locking path: 'C:\\a\\1\\b\\_locks\\ansi-styles-cedcc1e1e4774cd0.lock.STALE.STALE.STALE' }
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "--dev" "--cache" "C:\\a\\1\\b"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! Attempt to unlock C:\a\1\s\com.example.web\node_modules\gulp-imagemin\node_modules\imagemin-pngquant\node_modules\pngquant-bin\node_modules\compare-size\node_modules\ava\node_modules\chalk\node_modules\ansi-styles, which hasn't been locked
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm WARN locking Error: EMFILE, open 'C:\a\1\b\_locks\has-ansi-819c7cca16ab7ac8.lock.STALE.STALE.STALE'
npm WARN locking at Error (native)
2016-03-30T14:15:17.5709240Z npm WARN locking C:\a\1\b\_locks\has-ansi-819c7cca16ab7ac8.lock failed { [Error: EMFILE, open 'C:\a\1\b\_locks\has-ansi-819c7cca16ab7ac8.lock.STALE.STALE.STALE']
Re-installing NPM solved my issue:
npm install npm -g
Specifically, I added the circled task to my build: