how to solve this issue and run npm install?-CodePudding

I am trying to run npm install so I can do yarn start to deploy the project to was but it gives me an error. Anyone here can help me understand what is going on and how to solve it?

The Error output here:

npm WARN tarball tarball data for proto@git https://github.com/ArtistCrowdfundExchange/proto.git (null) seems to be corrupted. Trying again.
npm WARN tarball tarball data for proto@git https://github.com/ArtistCrowdfundExchange/proto.git (null) seems to be corrupted. Trying again.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /Users/youmnasalloum/.npm/_cacache/tmp/git-cloneEiauOJ/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/Users/youmnasalloum/.npm/_cacache/tmp/git-cloneEiauOJ/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/youmnasalloum/.npm/_logs/2022-04-01T11_16_23_452Z-debug-0.log

The package.json content here:

{
  "name": "user",
  "version": "1.0.0",
  "main": "index.ts",
  "repository": "https://github.com/ArtistCrowdfundExchange/user",
  "author": "Oghogho Odemwingie",
  "license": "MIT",
  "devDependencies": {
    "@types/bcrypt": "^3.0.0",
    "@types/node": "^17.0.13",
    "typescript": "4.5.5"
  },
  "scripts": {
    "start": "ts-node index.ts",
    "test": "echo no tests yet"
  },
  "dependencies": {
    "@aws-sdk/client-s3": "^3.41.0",
    "@grpc/grpc-js": "^1.3.7",
    "aws4": "^1.11.0",
    "bcrypt": "^5.0.0",
    "cuid": "^2.1.8",
    "jose": "3",
    "mongoose": "6.1.8",
    "nanoid": "^3.1.29",
    "proto": "git https://github.com/ArtistCrowdfundExchange/proto#playground",
    "ts-node": "^10.4.0",
    "winston": "^3.3.3"
  }
}

CodePudding user response：

Same as @Mustafa Jawed and then make sure you are in the correct folder! if you use terminal use "ls" to see the content and go to to correct dictionary by for example "cd myExampleJsApp".

CodePudding user response：

Delete package-lock.json and rerun the npm i.

If this doesn't work then remove the node_modules and reinstall it.