Npm install error

Question & Answer Builds
1

Bitrise Build Issue Report template

Description of the issue

I’m getting error on npm install

npm ERR! code 128
npm ERR! Command failed: git clone --mirror -q GitHub - cordova-misc/cordova-webintent: WebIntent Android Plugin for Cordova 3.X /root/.npm/_cacache/tmp/git-clone-fdfdf265/.git
npm ERR! fatal: could not create leading directories of ‘/root/.npm/_cacache/tmp/git-clone-fdfdf265/.git’

Environment:

Where did the issue happen?

Android & Docker on Ubuntu 16.04

Which build Step causes the issue and which version of the step?

Run npm command (npm install)

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : every time
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : always

Looks like it’s not working when packages.json contains package with direct git link, like:
“cordova-support-google-services”: “git+https://github.com/LuisEGR/cordova-support-google-services.git”,

Local reproduction

locally works fine

Local reproduction: Linux / Android (docker based) stack builds

did not try

Build log

https://app.bitrise.io/build/c4ab6d4ffd39da06#?tab=log

2

this step is working on mac stack, but my next steps for ionic/android are not working on mac

3

Hi there @volser!

Could you please send us the URL of the build and also enable support access ( Enabling the Bitrise Support user for your app | Bitrise DevCenter)? :slight_smile:

4

image
image2666×234 21.6 KB

:rofl:

5

Done

build: https://app.bitrise.io/build/aa483e28baf8a545#?tab=log

6

We are seeing this same issue. Has a solution been found yet? Thank you!

7

Had same issue. The reason was update of npm with “npm install npm -g”, fixed when removed

1 Like
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.