pnpm / pnpm

Fast, disk space efficient package manager
https://pnpm.io
MIT License
29.47k stars 995 forks source link

 ERROR  ENOENT: no such file or directory, #1279

Closed zuohuadong closed 4 years ago

zuohuadong commented 6 years ago

image

zkochan commented 6 years ago

I thought I knew where the error was but I need more details.

After installation fails, can you check if the package.json exists? Does the directory that contain the package.json exist? If it exists, what does it contain? What other files are in .../body-parser/1.17.0/?

Also, it would be helpful if you would post your pnpm-debug.log which is created automatically when pnpm fails

zkochan commented 6 years ago

Also, please specify your Node.js version. I have noticed that different versions of Node.js behave differently when unpacking tarballs. You may get a more meaningful error with Node.js 8

zuohuadong commented 6 years ago
{
    "name": "visfit-lite-wechat",
    "version": "1.0.0",
    "description": "VF-Air wechat API",
    "bin":"package/server.js",
    "scripts": {
        "start": "ts-node -r tsconfig-paths/register src/server.ts",
        "start:dev": "nodemon",
        "start:debug": "nodemon --config nodemon-debug.json",
        "check": "tslint -p tsconfig.json -c tslint.json",
        "fix": "tslint -p tsconfig.json -c tslint.json --fix"
    },
    "author": "duanzeyao",
    "license": "MIT",
    "private": false,
    "dependencies": {
        "@nestjs/common": "^5.0.0",
        "@nestjs/core": "^5.0.0",
        "@nestjs/graphql": "^3.0.0",
        "@nestjs/microservices": "^5.0.1",
        "@nestjs/passport": "^1.0.11",
        "body-parser": "^1.18.3",
        "fastify": "^1.4.0",
        "fastify-formbody": "^2.0.0",
        "fastify-graphql-middleware": "^2.1.1",
        "fastify-static": "^0.12.0",
        "fastify-xml-body-parser": "^1.0.2",
        "graphql": "^0.13.2",
        "graphql-tools": "^3.0.1",
        "grpc": "^1.12.4",
        "jsonwebtoken": "^8.3.0",
        "moment": "^2.22.2",
        "passport": "^0.4.0",
        "passport-http-bearer": "^1.0.1",
        "passport-jwt": "^4.0.0",
        "reflect-metadata": "^0.1.12",
        "rxjs": "^6.1.0"
    },
    "devDependencies": {
        "@nestjs/testing": "^5.0.0",
        "@types/body-parser": "^1.17.0",
        "@types/graphql": "^0.13.1",
        "@types/jsonwebtoken": "^7.2.7",
        "@types/node": "^10.0.8",
        "@types/passport-jwt": "^3.0.1",
        "nodemon": "^1.17.4",
        "ts-node": "^6.0.3",
        "tsconfig-paths": "^3.3.2",
        "tslint": "^5.10.0",
        "typescript": "^2.8.3"
    }
}

node: 10.6.0

zuohuadong commented 6 years ago

@zkochan pnpm-debug.log

rahulsrivastava71 commented 4 years ago

facing the same issue

zkochan commented 4 years ago

The pnpm store has been changed completely in pnpm v5, so this exact error should not exist anymore.

Feel free to open a new issue if you have issues with the new store in pnpm v5.