Attempting to install a global NPM package, for example @angular/cli, results in a permission denied error.
The pipelines configuration is pretty simple:
image: atlassian/default-image:2pipelines: custom: production: - step: name: Build & Deploy Project deployment: production script: - npm install -g @angular/cli@6.0.0 - npm install -g gulp-cli - cd web/web.cmor - npm install - gulp prod - ng build --prod
The resulting failure reads like this:
<span>/root/.nvm/versions/node/v8.9.4/bin/ng -> /root/.nvm/versions/node/v8.9.4/lib/node_modules/@angular/cli/bin/ng</span><span>> @angular/cli@6.0.0 postinstall /root/.nvm/versions/node/v8.9.4/lib/node_modules/@angular/cli</span><span>> node ./bin/ng-update-message.js</span><span>sh: 1: node: Permission denied</span><span>npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.3 (node_modules/@angular/cli/node_modules/fsevents):</span><span>npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})</span><span>npm ERR! file sh</span><span>npm ERR! code ELIFECYCLE</span><span>npm ERR! errno ENOENT</span><span>npm ERR! syscall spawn</span><span>npm ERR! @angular/cli@6.0.0 postinstall: `node ./bin/ng-update-message.js`</span><span>npm ERR! spawn ENOENT</span><span>npm ERR! </span><span>npm ERR! Failed at the @angular/cli@6.0.0 postinstall script.</span><span>npm ERR! This is probably not a problem with npm. There is likely additional logging output above.</span><span>npm ERR! A complete log of this run can be found in:</span><span>npm ERR! /root/.npm/_logs/2018-05-08T16_23_15_479Z-debug.log</span><span>npm install -g @angular/cli@6.0.0</span>
