-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] "could not create leading directories" when installing globally from GitHub URL #642
Comments
Duplicate of #624. |
isaacs
added a commit
to npm/pacote
that referenced
this issue
Dec 30, 2019
Fix: npm/cli#624 Fix: npm/cli#642 Fix: npm/cli#514 Infer the ownership of a git command invocation based on the cwd, if one is specified.
Merged
rish9511
added a commit
to ElucidataInc/node-s3-client
that referenced
this issue
Jun 30, 2022
Before this commit it was required to install the package using Github. However when using NPM version 8.5, the installation used to fail with the following error : "... git --no-replace-objects clone https://git@github.com/ElucidataInc/node-s3-client.git /root/.npm/_cacache/tmp/git-cloneNZtpAU --recurse-submodules npm ERR! fatal: could not create leading directories of '/root/.npm/_cacache/tmp/git-cloneNZtpAU': Permission denied" The following Github threads were reported with similar issues - npm/cli#624 - npm/cli#642 As the suggested methods in the above threads, like shifting to older version of NPM, did not satisfy our needs, we are publishing the package to NPM public registry
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What / Why
npm: v5.8.0, v6.13.4
When I attempt to install a package from GitHub globally, I am getting a permission error: "could not create leading directories".
The relevant log bits:
When
Where
How
Current Behavior
Steps to Reproduce
Expected Behavior
Who
References
The text was updated successfully, but these errors were encountered: