Skip to content

[BUG] npm install followed by npm ci fails with no such file or directory (chmod failure) #2251

Closed
@tmanning

Description

@tmanning

Current Behavior:

When you run npm i successfully followed by npm ci the operation fails.

Expected Behavior:

When you run npm i successfully followed by npm ci it should complete without errors.

Steps to reproduce

package.json:

{
  "name": "testnpm",
  "version": "0.1.0",
  "devDependencies": {
    "aws-cdk": "1.75.0"
  },
  "dependencies": {}
}

npm i generates a package-lock.json
follow this with
npm ci
and it fails looking for node_modules/aws-cdk/bin/cdk

npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /Users/testing/project/node_modules/aws-cdk/bin/cdk
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/testing/project/node_modules/aws-cdk/bin/cdk'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm 6 does not exhibit this problem.

Environment:

  • OS: OSX 10.15.7
  • Node: 12.18.3
  • npm: 7.0.14

The same occurs on linux

Metadata

Metadata

Assignees

Labels

Bugthing that needs fixingPriority 1high priority issueRelease 7.xwork is associated with a specific npm 7 release

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions